Release v1.2.2
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
paydii committed
Jun 28, 2026 at 14:39 UTC
59a61452189f0cf2eeb118813f8b59ac98d233bf
4 files changed
+26
-2
.agents/skills/sigit-code-release/SKILL.md
+13
@@ -32,6 +32,18 @@ Use this skill when preparing a release for this repository.
32
- Release workflows are tag-driven. `release-github.yml`, `release-npm.yml`, `release-pypi.yml`, `release-crates.yml`, and `release-homebrew.yml` all derive `RELEASE_VERSION` from a `v*.*.*` tag or a manually supplied tag input.
33
- The crate is published to crates.io (`release-crates.yml`) and the Homebrew tap is updated (`release-homebrew.yml`) as part of the tag-driven flow. Per the siGit release flow, Homebrew is auto-triggered — do not dispatch it manually.
34
35
+## Git release flow
36
+
37
+Releases are cut from `development` and shipped on `main`. The published tags (`v1.2.0`, `v1.2.1`) point at the `main`-side merge commit, never at a release branch or at `development`. Follow this order:
38
+
39
+1. Branch `release/v<version>` off `development`.
40
+2. Apply the version bump and changelog edits, then commit (e.g. `Release v<version>`).
41
+3. Merge `release/v<version>` back into `development`.
42
+4. Merge `development` into `main` (commit message: `Merge development into main for v<version> release`).
43
+5. Tag `v<version>` on that `main` merge commit, then push `main` and the tag.
44
+
45
+Pushing the `v*.*.*` tag is what fires every release workflow, so create and push it only after the merge into `main` has landed. Do not commit, tag, or push until the user explicitly asks — confirm the version and that they want the release to go out first.
46
+
47
## Typical files to inspect
48
49
- `Cargo.toml`
@@ -52,6 +64,7 @@ Use this skill when preparing a release for this repository.
64
- `npm/sigit/package.json` is left at `0.0.0-dev` unless the packaging flow itself changed.
65
- `pypi/pyproject.toml` still uses dynamic versioning unless there is a deliberate packaging change.
66
- Release workflows still derive their version from the tag as expected.
67
+- Git flow followed: bump committed on `release/v<version>`, merged back to `development`, then `development` merged into `main`, with `v<version>` tagged on the `main` merge commit.
68
- Release notes or changelog entries match the actual changes.
69
- CI-equivalent local checks pass for the relevant platform or target.
70
- Package names, install commands, and branding stay consistent.
CHANGELOG.md
+11
@@ -1,5 +1,16 @@
1
# Changelog
2
3
+## 1.2.2
4
+
5
+Streams assistant tokens as they arrive, on-device and over the cloud.
6
+
7
+### What changed
8
+
9
+- Streamed assistant tokens live in the TUI and ACP sessions, both on-device and through siGit Code Cloud
10
+- On-device inference streams only when a turn offers no tools, since `onde` can't stream and detect tool calls in the same pass; tool-capable turns still resolve in one shot
11
+- Fixed the TUI so the latest message stays visible in long chats
12
+- Put the cloud model-switch confirmation on its own line in ACP
13
+
14
## 1.2.1
15
16
Stabilizes the Zed/ACP integration and finishes the cloud-tier wiring on top of 1.2.0.
Cargo.lock
+1
-1
@@ -5210,7 +5210,7 @@ checksum = "f8fadd59c855ef2080decdef8ff161eb6661b86933c9d82e5ba29dc602a55aba"
5210
5211
[[package]]
5212
name = "sigit"
5213
-version = "1.2.1"
5213
+version = "1.2.2"
5214
dependencies = [
5215
"agent-client-protocol",
5216
"anyhow",
Cargo.toml
+1
-1
@@ -1,6 +1,6 @@
1
[package]
2
name = "sigit"
3
-version = "1.2.1"
3
+version = "1.2.2"
4
edition = "2024"
5
description = "siGit Code — ACP-compatible AI coding agent. Sí, git."
6
documentation = "https://github.com/getsigit/sigit"