Release notes
HOL Guard v3.60.0a102
PreviewHOL Guard v3.60.0a102, released November 15, 2026, is a preview release with 1 fix and 1 other change across 1 merged pull request. Highlights: Keep Codex settings added after install when Guard is uninstalled.
1 fixed · 1 other
Key facts
- Version
- v3.60.0a102
- Channel
- Preview
- Published
- Previous release
- alpha/v3.60.0a101
- Merged pull requests
- 1
Documented changes
2 typed entries
Verified contributors
1 verified contributor · 1 credit
Attribution coverage
attribution complete; history inventory partial.
Install
Scope
Guard v3.60.0a102 is a preview release published 2026-11-15. Upstream documents: Guard 3.60.0a102 is an opt-in prerelease cut from 2e5c983. Stable installations remain on the stable channel. 1 commit • 1 merged pull request • 1 contributor since Guard 3.60.0a101. Its comparison base is alpha/v3.60.0a101. It includes 1 verified contribution delivery with public evidence links.
Changes
Fixed
1- guardKeep Codex settings added after install when Guard is uninstalled (#7840) Evidence for this change
- Each MCP server that launches through Guard's proxy gets back its pre-install entry, or is removed when it had none. Servers added after install stay.
- Guard's hook groups are removed (manifest-bound, legacy and current-install bindings, as before). The user's own hooks stay.
- When no hook group is left,
features.hooksandfeatures.codex_hooksreturn to their pre-install values. When the user's hooks remain, the feature stays on so they keep running. - Merged pull request #7840: fix(guard): keep Codex settings added after install when Guard is uninstalled
Other changes
1- Guard 3.60.0a102 is an opt-in prerelease cut from
2e5c983. Stable installations remain on the stable channel. 1 commit • 1 merged pull request • 1 contributor since Guard 3.60.0a101. Evidence for this change
Upgrade and compatibility
None documented.
Compare with the previous release
Predecessor on the same channel: alpha/v3.60.0a101
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.