Release v1.5.5
paydii committed
Aug 31, 2026 at 18:59 UTC
029a2fe2089bf4f9414f5abc293da09e3eba31a2
3 files changed
+24
-2
CHANGELOG.md
+22
@@ -1,5 +1,27 @@
1
# Changelog
2
3
+## 1.5.5
4
+
5
+A distribution release. siGit Code itself is unchanged. What moved is how it
6
+reaches you on npm and on Windows.
7
+
8
+### What changed
9
+
10
+- **The npm package is now `@getsigit/sigit`.** The six platform packages moved
11
+ with it. `@smbcloud/sigit` stays on the registry but stops receiving updates,
12
+ so upgrading means switching names:
13
+ `npm uninstall -g @smbcloud/sigit && npm install -g @getsigit/sigit`. The old
14
+ package had been stuck at 1.5.2, so this picks up 1.5.3 and 1.5.4 as well.
15
+- **npm publishes over OIDC.** Every `@getsigit/*` package has a trusted
16
+ publisher pointing at the release workflow, so no npm token is stored in the
17
+ repository. The release workflow moves to Node 22, which trusted publishing
18
+ requires.
19
+- **winget releases actually go out.** The workflow could only update a package
20
+ already present in `microsoft/winget-pkgs`, and siGit Code had never been
21
+ submitted there, so every dispatch failed. It now submits the package the
22
+ first time and updates it on later releases. The identifier is
23
+ `getSigit.siGitCode`.
24
+
25
## 1.5.4
26
27
- **CI**: nfpm config expanded to include package version and binary path
Cargo.lock
+1
-1
@@ -5778,7 +5778,7 @@ checksum = "f8fadd59c855ef2080decdef8ff161eb6661b86933c9d82e5ba29dc602a55aba"
5778
5779
[[package]]
5780
name = "sigit"
5781
-version = "1.5.4"
5781
+version = "1.5.5"
5782
dependencies = [
5783
"agent-client-protocol",
5784
"anyhow",
Cargo.toml
+1
-1
@@ -1,6 +1,6 @@
1
[package]
2
name = "sigit"
3
-version = "1.5.4"
3
+version = "1.5.5"
4
edition = "2024"
5
description = "siGit Code — ACP-compatible AI coding agent. Sí, git."
6
documentation = "https://github.com/getsigit/sigit"