Release notes
HOL Guard v3.60.0a14
PreviewHOL Guard v3.60.0a14, released November 6, 2026, is a preview release with 3 additions, 1 improvement, 2 fixes and 1 other change across 6 merged pull requests. Highlights: Write earned authority anchors in the resident; Resume a commit retry's own prepared row in the resident.
3 added · 1 improved · 2 fixed · 1 other
Key facts
- Version
- v3.60.0a14
- Channel
- Preview
- Published
- Previous release
- alpha/v3.60.0a13
- Merged pull requests
- 6
Documented changes
7 typed entries
Verified contributors
1 verified contributor · 6 credits
Attribution coverage
attribution complete; history inventory partial.
Install
Scope
Guard v3.60.0a14 is a preview release published 2026-11-06. Upstream documents: Guard 3.60.0a14 is an opt-in prerelease cut from f7d8389. Stable installations remain on the stable channel. 6 commits • 6 merged pull requests • 1 contributor since Guard 3.60.0a13. Its comparison base is alpha/v3.60.0a13. It includes 6 verified contribution deliveries with public evidence links.
Changes
Added
3- extensionsWrite earned authority anchors in the resident (#7303) Evidence for this change
anchored: a prepared row exists at that revision, seals that snapshot, and carries no authority of its own. The vault still pins the committed head below it and the row authenticates as that head's prepare.committed: the committed snapshot head is that revision and digest, and the vault already names it.- Anything else, including
prepared, is refused as tampered with the vault untouched.
- extensionsResume a commit retry's own prepared row in the resident (#7301) Evidence for this change
- commit_pending / mark_committed / finish: the proof is inserted as consumed, or a reserved proof is stamped once (
coalesce), in the transaction that commits the row. - abandon: the reserved proof is released with the row.
- current: when the retry's view already shows the row committed, the proof is stamped and the change event queued; no anchor is written.
- commit_pending / mark_committed / finish: the proof is inserted as consumed, or a reserved proof is stamped once (
- extensionsMigrate a catalog that activates a command pack in the resident (#7300) Evidence for this change
migratetakes thepack_reservethe commit path already sends. It reserves the staged activation in the transaction that writes the prepared row and returnspack_boundonce the row is anchored. A reservation the…resumewith amigration_recordrecords the migration event in the transaction that commits the row. It queues no change event, which matches every other migration.- Python runs the same resume loop a commit uses, so the lifecycle floor moves before the resident installs the activation. The Python insert, reserve, finish, snapshot update and event write for this path are gone.
Improved
1- authorityRetire the Python pack activation journal writers (#7304) Evidence for this change
- Merged pull request #7300: feat(extensions): migrate a catalog that activates a command pack in the resident (#7300)
- Merged pull request #7304: refactor(authority): retire the Python pack activation journal writers (#7304)
- Merged pull request #7316: fix(command): let a Git Allow settle Git's own plumbing names (#7316)
- Merged pull request #7303: feat(extensions): write earned authority anchors in the resident (#7303)
- Merged pull request #7301: feat(extensions): resume a commit retry's own prepared row in the resident (#7301)
- Merged pull request #7314: fix(hook-core): keep field boundaries when scanning a structured edit (#7314)
Fixed
2- hook-coreKeep field boundaries when scanning a structured edit (#7314) Evidence for this change
- commandLet a Git Allow settle Git's own plumbing names (#7316) Evidence for this change
Other changes
1- Guard 3.60.0a14 is an opt-in prerelease cut from
f7d8389. Stable installations remain on the stable channel. 6 commits • 6 merged pull requests • 1 contributor since Guard 3.60.0a13. Evidence for this change
Upgrade and compatibility
None documented.
Compare with the previous release
Predecessor on the same channel: alpha/v3.60.0a13
Verified contributors
Credits derive from public pull-request authorship, verified commit authorship, or verified co-authorship — never from thanks text or release metadata. Each distinct contributor is listed once; the evidence ledger paginates every published credit record.