v1.0.4

index 0aa0cbe..83ce33c 100644 --- a/.agents/skills/sigit-code-release/SKILL.md +++ b/.agents/skills/sigit-code-release/SKILL.md @@ -10,16 +10,26 @@ Use this skill when preparing a release for this repository. ## Focus areas - Keep the branded product name as `siGit Code` in prose and `sigit` for commands, crate names, repo paths, and package identifiers. -- Verify version consistency across release surfaces such as `Cargo.toml`, lockfiles if applicable, npm packaging files, Python packaging files, and user-facing install docs. +- Verify version consistency across release surfaces, but respect which files are real sources of truth versus generated or release-time rewritten artifacts. - Check release-facing docs such as `README.md`, `CHANGELOG.md`, workflow notes, and package metadata for stale version references or incorrect naming. - Validate the local release path pragmatically: formatting, linting, targeted tests, and any repo-specific release checks that matter for the requested version. ## Working approach 1. Read the files that define the release version and distribution metadata before proposing any changes. -2. Compare version strings across Rust, npm, Python, and docs instead of assuming they stay in sync automatically. -3. Prefer targeted verification commands that match CI or packaging workflows already present in the repository. -4. Report blockers clearly: failed checks, version mismatches, missing changelog entries, or unpublished packaging changes. +2. Treat `Cargo.toml` as the primary release version source for the Rust crate and the PyPI package in this repository. +3. Check how the release workflows rewrite or derive versions before editing checked-in npm or Python metadata. +4. Prefer targeted verification commands that match CI or packaging workflows already present in the repository. +5. Report blockers clearly: failed checks, version mismatches, missing changelog entries, or unpublished packaging changes. + +## Repo-specific release rules + +- Bump the crate version in `Cargo.toml`. +- Update the root `sigit` package entry in `Cargo.lock` when the crate version changes. +- Add or update the top changelog entry in `CHANGELOG.md` for the release being cut. +- Do not treat `npm/sigit/package.json` `0.0.0-dev` as a bug by default. The npm release workflow rewrites it at publish time using `npm/scripts/render-main-package.cjs` and the release tag. +- Do not add a hardcoded version to `pypi/pyproject.toml` for normal releases. PyPI uses `maturin` with `dynamic = ["version"]` and derives the published package version from `Cargo.toml`. +- Release workflows are tag-driven. `release-github.yml`, `release-npm.yml`, and `release-pypi.yml` all derive `RELEASE_VERSION` from a `v*.*.*` tag or a manually supplied tag input. ## Typical files to inspect @@ -27,6 +37,8 @@ Use this skill when preparing a release for this repository. - `Cargo.lock` - `CHANGELOG.md` - `README.md` +- `npm/sigit/package.json` +- `npm/scripts/render-main-package.cjs` - `npm/` - `pypi/` - `.github/workflows/` @@ -34,6 +46,11 @@ Use this skill when preparing a release for this repository. ## Release checklist - Version bump is applied everywhere it needs to be. +- `Cargo.toml` and the root crate entry in `Cargo.lock` match. +- `CHANGELOG.md` has a correct top entry for the new release. +- `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. - 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 f2aa607..93ee700 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,15 @@ # Changelog +## 1.0.4 + +This release tightens up the terminal experience and finishes a few release-facing cleanup items. + +### What changed + +- Added bold rich-text rendering in the TUI for assistant replies, so `**text**` now displays with terminal styling instead of raw markdown markers +- Refreshed the bundled skill metadata to follow the current Agent Skills `SKILL.md` format +- Synced the crate release metadata for the `1.0.4` cut + ## 1.0.3 This is the cleanup release for the editor-side startup problems. @@ -143,4 +153,4 @@ ACP and editor mode work on Windows. The part that is still missing is the inter --- -*© 2026 [smbCloud](https://smbcloud.xyz/) (Splitfire AB).* \ No newline at end of file +*© 2026 [smbCloud](https://smbcloud.xyz/) (Splitfire AB).*

index 22a3c3f..0d1f208 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -4987,7 +4987,7 @@ checksum = "f8fadd59c855ef2080decdef8ff161eb6661b86933c9d82e5ba29dc602a55aba" [[package]] name = "sigit" -version = "1.0.3" +version = "1.0.4" dependencies = [ "agent-client-protocol", "anyhow",

index 0e6b08b..23471ee 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "sigit" -version = "1.0.3" +version = "1.0.4" edition = "2024" description = "siGit Code — ACP-compatible AI coding agent. Sí, git." documentation = "https://github.com/getsigit/sigit"