Release notes
HOL Guard v3.60.0a100
PreviewHOL Guard v3.60.0a100, released November 15, 2026, is a preview release with 1 addition, 7 fixes and 3 other changes across 10 merged pull requests. Highlights: Preselect the exact action and state each approval scope's terms; Settle a gh response filter written over several lines.
1 added · 7 fixed · 3 other
Key facts
- Version
- v3.60.0a100
- Channel
- Preview
- Published
- Previous release
- alpha/v3.60.0a99
- Merged pull requests
- 10
Documented changes
11 typed entries
Verified contributors
1 verified contributor · 10 credits
Attribution coverage
attribution complete; history inventory partial.
Install
Scope
Guard v3.60.0a100 is a preview release published 2026-11-15. Upstream documents: Guard 3.60.0a100 is an opt-in prerelease cut from 37f1de8. Stable installations remain on the stable channel. 10 commits • 10 merged pull requests • 1 contributor since Guard 3.60.0a99. Its comparison base is alpha/v3.60.0a99. It includes 10 verified contribution deliveries with public evidence links.
Changes
Added
1- guardPreselect the exact action and state each approval scope's terms (#7820) Evidence for this change
- Rust scope contract (
approval_scope_contract.rs): the recommended allow scope is now the exact reviewed action whenever it is offered. The project scope is recommended only when the exact action is not offered.… - Dashboard: every scope choice states three things: Applies to, Expires, and Policy (whether anything is saved, and where). Broader scopes always show these terms. The exact-action choice shows them once…
- Docs:
docs/guard/approval-invariant.mdgains a Scope choices section.
- Rust scope contract (
Fixed
7- guardSettle a gh response filter written over several lines (#7824) Evidence for this change
- guardAllow cp -c, -p and -v, and cp -R into a private temporary directory (#7814) Evidence for this change
- guardTell the agent when a Cloud Review request expired unanswered (#7821) Evidence for this change
- guardAllow mkdir -p of an existing scratch folder and rm of the agent's own scratch file (#7816) Evidence for this change
- guardLet a tee stage that saves both output streams settle like its redirect (#7818) Evidence for this change
- cigarTell Claude Code a passing check ends the change and how to read a failed doctest (#7809) Evidence for this change
- cigarList a test class that inherits its tests from a mixin (#7812) Evidence for this change
Other changes
3- Guard 3.60.0a100 is an opt-in prerelease cut from
37f1de8. Stable installations remain on the stable channel. 10 commits • 10 merged pull requests • 1 contributor since Guard 3.60.0a99. Evidence for this change - gauntletName a prompt Guard stopped instead of calling it a host failure (#7819) Evidence for this change
- gauntletLet eight protection prompts reach the tool call Guard must stop (#7817) Evidence for this change
- Merged pull request #7818: fix(guard): let a tee stage that saves both output streams settle like its redirect
- Merged pull request #7809: fix(cigar): tell Claude Code a passing check ends the change and how to read a failed doctest
- Merged pull request #7816: fix(guard): allow mkdir -p of an existing scratch folder and rm of the agent's own scratch file
- Merged pull request #7821: fix(guard): tell the agent when a Cloud Review request expired unanswered
- Merged pull request #7817: test(gauntlet): let eight protection prompts reach the tool call Guard must stop
- Merged pull request #7824: fix(guard): settle a gh response filter written over several lines
- Merged pull request #7812: fix(cigar): list a test class that inherits its tests from a mixin
- Merged pull request #7819: test(gauntlet): name a prompt Guard stopped instead of calling it a host failure
- Merged pull request #7814: fix(guard): allow cp -c, -p and -v, and cp -R into a private temporary directory
- Merged pull request #7820: feat(guard): preselect the exact action and state each approval scope's terms
Upgrade and compatibility
None documented.
Compare with the previous release
Predecessor on the same channel: alpha/v3.60.0a99
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.