4 files changed
+34
-7
.agents/skills/sigit-code-release/SKILL.md
+21
-4
@@ -10,16 +10,26 @@ Use this skill when preparing a release for this repository.
10
## Focus areas
11
12
- Keep the branded product name as `siGit Code` in prose and `sigit` for commands, crate names, repo paths, and package identifiers.
13
-- Verify version consistency across release surfaces such as `Cargo.toml`, lockfiles if applicable, npm packaging files, Python packaging files, and user-facing install docs.
13
+- Verify version consistency across release surfaces, but respect which files are real sources of truth versus generated or release-time rewritten artifacts.
14
- Check release-facing docs such as `README.md`, `CHANGELOG.md`, workflow notes, and package metadata for stale version references or incorrect naming.
15
- Validate the local release path pragmatically: formatting, linting, targeted tests, and any repo-specific release checks that matter for the requested version.
16
17
## Working approach
18
19
1. Read the files that define the release version and distribution metadata before proposing any changes.
20
-2. Compare version strings across Rust, npm, Python, and docs instead of assuming they stay in sync automatically.
21
-3. Prefer targeted verification commands that match CI or packaging workflows already present in the repository.
22
-4. Report blockers clearly: failed checks, version mismatches, missing changelog entries, or unpublished packaging changes.
20
+2. Treat `Cargo.toml` as the primary release version source for the Rust crate and the PyPI package in this repository.
21
+3. Check how the release workflows rewrite or derive versions before editing checked-in npm or Python metadata.
22
+4. Prefer targeted verification commands that match CI or packaging workflows already present in the repository.
23
+5. Report blockers clearly: failed checks, version mismatches, missing changelog entries, or unpublished packaging changes.
24
+
25
+## Repo-specific release rules
26
+
27
+- Bump the crate version in `Cargo.toml`.
28
+- Update the root `sigit` package entry in `Cargo.lock` when the crate version changes.
29
+- Add or update the top changelog entry in `CHANGELOG.md` for the release being cut.
30
+- 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.
31
+- 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`.
32
+- 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.
33
34
## Typical files to inspect
35
@@ -27,6 +37,8 @@ Use this skill when preparing a release for this repository.
37
- `Cargo.lock`
38
- `CHANGELOG.md`
39
- `README.md`
40
+- `npm/sigit/package.json`
41
+- `npm/scripts/render-main-package.cjs`
42
- `npm/`
43
- `pypi/`
44
- `.github/workflows/`
@@ -34,6 +46,11 @@ Use this skill when preparing a release for this repository.
46
## Release checklist
47
48
- Version bump is applied everywhere it needs to be.
49
+- `Cargo.toml` and the root crate entry in `Cargo.lock` match.
50
+- `CHANGELOG.md` has a correct top entry for the new release.
51
+- `npm/sigit/package.json` is left at `0.0.0-dev` unless the packaging flow itself changed.
52
+- `pypi/pyproject.toml` still uses dynamic versioning unless there is a deliberate packaging change.
53
+- Release workflows still derive their version from the tag as expected.
54
- Release notes or changelog entries match the actual changes.
55
- CI-equivalent local checks pass for the relevant platform or target.
56
- Package names, install commands, and branding stay consistent.
CHANGELOG.md
+11
-1
@@ -1,5 +1,15 @@
1
# Changelog
2
3
+## 1.0.4
4
+
5
+This release tightens up the terminal experience and finishes a few release-facing cleanup items.
6
+
7
+### What changed
8
+
9
+- Added bold rich-text rendering in the TUI for assistant replies, so `**text**` now displays with terminal styling instead of raw markdown markers
10
+- Refreshed the bundled skill metadata to follow the current Agent Skills `SKILL.md` format
11
+- Synced the crate release metadata for the `1.0.4` cut
12
+
13
## 1.0.3
14
15
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
153
154
---
155
146
-*© 2026 [smbCloud](https://smbcloud.xyz/) (Splitfire AB).*
\ No newline at end of file
156
+*© 2026 [smbCloud](https://smbcloud.xyz/) (Splitfire AB).*
Cargo.lock
+1
-1
@@ -4987,7 +4987,7 @@ checksum = "f8fadd59c855ef2080decdef8ff161eb6661b86933c9d82e5ba29dc602a55aba"
4987
4988
[[package]]
4989
name = "sigit"
4990
-version = "1.0.3"
4990
+version = "1.0.4"
4991
dependencies = [
4992
"agent-client-protocol",
4993
"anyhow",
Cargo.toml
+1
-1
@@ -1,6 +1,6 @@
1
[package]
2
name = "sigit"
3
-version = "1.0.3"
3
+version = "1.0.4"
4
edition = "2024"
5
description = "siGit Code — ACP-compatible AI coding agent. Sí, git."
6
documentation = "https://github.com/getsigit/sigit"