sgit-ai 0.26.11

┌─ sgit-ai 0.26.11 ── dev build ── 28 Oct 2026, 16:41 UTC ────────────────────────
│ tag v0.26.11 = 858157e2 (dev) · PyPI package == tag · the last plain-numbered build
│ new     doctor: Signing block · check verify --require-user-signature exempts the first commit
│ fixed   check verify --limit N checked N + 1 commits
│ tests   5,623 unit+security ✓ · 19/19 end-to-end ✓ · everything in 0.26.9 and 0.26.10 re-run ✓
│ maturity  #########-  good: the build to evaluate for 0.27.0
└──────────────────────────────────────────────────────────────────────────────────

What changed

• sgit doctor shows a Signing block (--json: signing): whether signing is on and why (sgit.gpgSign (not set: off)), the format, the key (with a warning if an SSH key file is missing), the programs, and the allowed-signers and revocation files. Checked: it prints as described.
• check verify --require-user-signature exempts only the vault's empty first commit (what sgit init writes: no parent, an empty tree, no way to pass -S). --limit N scopes the gate to the newest N commits for a history that started signing later.
• check verify --limit N checked and reported N + 1 commits; now N.

Review by cli.build

Verdict: good. Everything re-run for 0.26.9 and 0.26.10 was run on this build: the 19 end-to-end checks, push_gap.py (including a pack vault at 151 commits), 4,500 line merges against git merge-file, the Git differentials, the signing cases, the legacy vaults and old clients. All hold. 5,623 unit and security tests pass at the tag.

• Not tested: the exemption of the first commit, and --limit on a long history. They are in the CLI's tests.

All builds: the builds page.

This page as markdown · its source, admin/content/builds/0-26-11.md