Skip to content

release: 0.14.0 - #391

Merged
vladimirrott merged 1 commit into
mainfrom
release-0.14.0
Sep 7, 2026
Merged

vladimirrott merged 1 commit into
mainfrom
release-0.14.0

Conversation

@vladimirrott

Copy link
Copy Markdown
Member

Version bump and CHANGELOG for 0.14.0.

Why the middle digit

sysknife audit checkpoint with no database configured returned exit 2 and now returns exit 4 (#381). docs/cli.md calls the exit codes the contract a wrapper script reads, and docs/release.md#version-numbering is explicit that behaviour counts and not only signatures:

v0.9.0 also made sysknife-setup refuse a malformed .mcp.json that earlier versions overwrote, so a run that used to succeed now exits 1. No signature changed and it is still a compatibility break.

So this is 0.14.0 rather than 0.13.2, and it would have been even without the API change queued in #384.

What is in it

Two fixes in the daemon's authorization path:

Plus the CLI exit-code contract (#381), the release-pin check that was filtering out the one broken pin it existed to catch (#378), single-source story metadata (#386), derived markdown link coverage (#376), and a dead daemon lock arm (#375).

The lockfile

Cargo.lock was regenerated by cargo, not edited. phf, phf_codegen, phf_generator, phf_macros and phf_shared are also pinned at 0.13.1, so substituting the string across the lockfile would have moved five unrelated crates to a version that does not exist. Only the 8 workspace crates moved; phf is untouched.

Verification

test_baseline: 1845 rust tests, matching the recorded baseline
Public claims contract passed
release-version-pins: missing inline versions fail explicitly
All release versions match 0.14.0 (15 internal dependency pins checked)
Registry preflight: sysknife-types/brain/daemon/cli  0.14.0 available

The middle digit moves because an exit code changed. `sysknife audit
checkpoint` with no database configured returned 2 and now returns 4, and
docs/cli.md calls the exit codes the contract a wrapper script reads.
docs/release.md#version-numbering is explicit that behaviour counts and not
only signatures, with v0.9.0 as the worked example.

Two of the fixes in this release are in the daemon's authorization path: a
cancelled transaction could keep a live approval receipt, and a peer the kernel
could not pin was still credited with the supplementary groups of whatever
process held that PID by the time /proc was read.

Bumps 14 manifests and the 15 internal path pins. Cargo.lock was regenerated
rather than edited: phf and its four siblings are also pinned at 0.13.1, so a
blind substitution would have moved them to a version that does not exist.

Verified: 1,845 tests pass and match the recorded baseline, public claims are
consistent, release-version-pins passes, check_release_versions.sh reports all
15 pins at 0.14.0, and the registry preflight finds 0.14.0 free for all four
published crates.
@vladimirrott
vladimirrott merged commit c82bb1f into main Sep 7, 2026
12 checks passed
@vladimirrott
vladimirrott deleted the release-0.14.0 branch September 7, 2026 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant