Release notes
HOL Guard v3.60.0a113
PreviewHOL Guard v3.60.0a113, released November 18, 2026, is a preview release with 2 fixes and 1 other change across 2 merged pull requests. Highlights: Do not score Codex daemon-auth failures as attack protection; Authenticate the Codex hooks a frozen bundle installs.
2 fixed · 1 other
Key facts
- Version
- v3.60.0a113
- Channel
- Preview
- Published
- Previous release
- alpha/v3.60.0a112
- Merged pull requests
- 2
Documented changes
3 typed entries
Verified contributors
1 verified contributor · 2 credits
Attribution coverage
attribution complete; history inventory partial.
Install
Scope
Guard v3.60.0a113 is a preview release published 2026-11-18. Upstream documents: Guard 3.60.0a113 is an opt-in prerelease cut from 1631e4a. Stable installations remain on the stable channel. 2 commits • 2 merged pull requests • 1 contributor since Guard 3.60.0a112. Its comparison base is alpha/v3.60.0a112. It includes 2 verified contribution deliveries with public evidence links.
Changes
Fixed
2- gauntletDo not score Codex daemon-auth failures as attack protection (#7921) Evidence for this change
- guardAuthenticate the Codex hooks a frozen bundle installs (#7950) Evidence for this change
- Package (wheel) installs still bind the exact runtime path.
- A retained frozen generation still needs the compatibility hash of the argv it actually registered.
- Every event of a generation must register the same argv.
- Merged pull request #7921: fix(gauntlet): do not score Codex daemon-auth failures as attack protection
- Merged pull request #7950: fix(guard): authenticate the Codex hooks a frozen bundle installs
Other changes
1- Guard 3.60.0a113 is an opt-in prerelease cut from
1631e4a. Stable installations remain on the stable channel. 2 commits • 2 merged pull requests • 1 contributor since Guard 3.60.0a112. Evidence for this change
Upgrade and compatibility
None documented.
Compare with the previous release
Predecessor on the same channel: alpha/v3.60.0a112
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.