Release v1.2.2

index 7dbd758..70afe90 100644 --- a/.agents/skills/sigit-code-release/SKILL.md +++ b/.agents/skills/sigit-code-release/SKILL.md @@ -32,6 +32,18 @@ Use this skill when preparing a release for this repository. - 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. - 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. +## Git release flow + +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: + +1. Branch `release/v<version>` off `development`. +2. Apply the version bump and changelog edits, then commit (e.g. `Release v<version>`). +3. Merge `release/v<version>` back into `development`. +4. Merge `development` into `main` (commit message: `Merge development into main for v<version> release`). +5. Tag `v<version>` on that `main` merge commit, then push `main` and the tag. + +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. + ## Typical files to inspect - `Cargo.toml` @@ -52,6 +64,7 @@ Use this skill when preparing a release for this repository. - `npm/sigit/package.json` is left at `0.0.0-dev` unless the packaging flow itself changed. - `pypi/pyproject.toml` still uses dynamic versioning unless there is a deliberate packaging change. - Release workflows still derive their version from the tag as expected. +- 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. - Release notes or changelog entries match the actual changes. - CI-equivalent local checks pass for the relevant platform or target. - Package names, install commands, and branding stay consistent.

index 9499194..0c94f62 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,16 @@ # Changelog +## 1.2.2 + +Streams assistant tokens as they arrive, on-device and over the cloud. + +### What changed + +- Streamed assistant tokens live in the TUI and ACP sessions, both on-device and through siGit Code Cloud +- 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 +- Fixed the TUI so the latest message stays visible in long chats +- Put the cloud model-switch confirmation on its own line in ACP + ## 1.2.1 Stabilizes the Zed/ACP integration and finishes the cloud-tier wiring on top of 1.2.0.

index 0d711f1..9727ffe 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -5210,7 +5210,7 @@ checksum = "f8fadd59c855ef2080decdef8ff161eb6661b86933c9d82e5ba29dc602a55aba" [[package]] name = "sigit" -version = "1.2.1" +version = "1.2.2" dependencies = [ "agent-client-protocol", "anyhow",

index 043ef63..4840706 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "sigit" -version = "1.2.1" +version = "1.2.2" edition = "2024" description = "siGit Code — ACP-compatible AI coding agent. Sí, git." documentation = "https://github.com/getsigit/sigit"