release: 0.14.0 - #391
Merged
Merged
release: 0.14.0#391
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump and CHANGELOG for 0.14.0.
Why the middle digit
sysknife audit checkpointwith no database configured returned exit 2 and now returns exit 4 (#381).docs/cli.mdcalls the exit codes the contract a wrapper script reads, anddocs/release.md#version-numberingis explicit that behaviour counts and not only signatures: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:
claim_approved_for_executioncould still consume it (fix: revoke approvals when queued work is canceled #380, closes Cancel and the TTL sweep end an approval without revoking it or writing an event #251)/procwas read (fix(daemon): fail closed when a peer cannot be pinned #382, closes peer_pidfd cannot tell a pre-6.5 kernel from a peer that already exited, so the PID-reuse check is off in the reuse case #250)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.lockwas regenerated bycargo, not edited.phf,phf_codegen,phf_generator,phf_macrosandphf_sharedare 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;phfis untouched.Verification