Release notes
HOL Guard v3.60.0a73
PreviewHOL Guard v3.60.0a73, released November 12, 2026, is a preview release with 1 addition, 7 fixes and 1 other change across 8 merged pull requests. Highlights: Add UluP Nexus read-only remote MCP contribution; Let openssl dgst print a file's digest.
1 added · 7 fixed · 1 other
Key facts
- Version
- v3.60.0a73
- Channel
- Preview
- Published
- Previous release
- alpha/v3.60.0a72
- Merged pull requests
- 8
Documented changes
9 typed entries
Verified contributors
Credits being verified. Attribution coverage is in progress.
Attribution coverage
attribution in progress; history inventory partial.
Install
Scope
Guard v3.60.0a73 is a preview release published 2026-11-12. Upstream documents: Guard 3.60.0a73 is an opt-in prerelease cut from a1d3f41. Stable installations remain on the stable channel. 8 commits • 8 merged pull requests • 2 contributors since Guard 3.60.0a72. Its comparison base is alpha/v3.60.0a72. It includes 9 verified contribution deliveries with public evidence links. Attribution for this release is being verified.
Changes
Added
1- Add UluP Nexus read-only remote MCP contribution (#7565) Evidence for this change
- Merged pull request #7543: fix(guard): read tracked documents under feature directories named for auth
- Merged pull request #7565: Add UluP Nexus read-only remote MCP contribution
- Merged pull request #7563: fix(guard): let a reader whose glob matches nothing proceed
- Merged pull request #7561: fix(daemon): keep a slow-starting Desktop Core alive instead of killing it at the start deadline
- Direct commit a802f2ef5dbb: Add external trust binding for UluP Nexus MCP
- Merged pull request #7532: fix(guard): let openssl dgst print a file's digest
- Merged pull request #7558: fix(guard): clear a recursive grep written with escaped alternatives or several patterns
- Merged pull request #7560: fix(guard): let sed delete, quit and rewrite addressed lines of a file it reads
- Merged pull request #7545: fix(guard): read a recursive grep whose exclusions follow the operands
Fixed
7- guardLet openssl dgst print a file's digest (#7532) Evidence for this change
- daemonKeep a slow-starting Desktop Core alive instead of killing it at the start deadline (#7561) Evidence for this change
- At the deadline, a child that is still running counts as starting only on evidence that just the spawned launch can produce:
- signed daemon state that binds this launch's nonce, or
- a heartbeat the frozen entry point writes before it imports Guard. The heartbeat has to carry this launch's nonce, be recorded after the spawn, fall inside a 180-second window, and name a pid in the spawned process tree.
- guardClear a recursive grep written with escaped alternatives or several patterns (#7558) Evidence for this change
- guardLet a reader whose glob matches nothing proceed (#7563) Evidence for this change
- guardLet sed delete, quit and rewrite addressed lines of a file it reads (#7560) Evidence for this change
- guardRead a recursive grep whose exclusions follow the operands (#7545) Evidence for this change
- A late exclusion is never counted as narrowing the walk. The operands must be safe to search in full, so a tree that needs the exclusion to hide a key still asks.
- Only the attached spelling (
--exclude-dir=NAME,--exclude=GLOB) is accepted. In the separated form--exclude-dir NAME,NAMEwould become a search root underPOSIXLY_CORRECT, so that form keeps its review. - Under the operand reading the word has to name nothing grep could open. No entry in the working directory may start with
--exclude(compared without case), and no other segment may create a file first. That also…
- guardRead tracked documents under feature directories named for auth (#7543) Evidence for this change
Other changes
1- Guard 3.60.0a73 is an opt-in prerelease cut from
a1d3f41. Stable installations remain on the stable channel. 8 commits • 8 merged pull requests • 2 contributors since Guard 3.60.0a72. Evidence for this change
Upgrade and compatibility
None documented.
Compare with the previous release
Predecessor on the same channel: alpha/v3.60.0a72
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.