Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript

Say in the upgrade notice that unpushed strict-source commits from before this release are scanned once

garrytand6decb78655f
diff --git a/behavior-changes.d/managed_push_scan_every_publish_gst2650.md b/behavior-changes.d/managed_push_scan_every_publish_gst2650.md
index 6d74cb3b77..459d34ae57 100644
--- a/behavior-changes.d/managed_push_scan_every_publish_gst2650.md
+++ b/behavior-changes.d/managed_push_scan_every_publish_gst2650.md
@@ -1 +1 @@
-A managed worktree now scans every push it makes for secrets, including the generated-page commits the dream cycle writes through and a push handed over from a busy publish lock, which used to go out unscanned. Only the commits the remote lacks are scanned, never history it already holds. A credential in an unpushed commit, or a false positive there, holds the push with `publish_secret_found` naming the file, line and rule, never the value; remove it from the commit or add its fingerprint to `.gbrain-scan-allow`, then run `gbrain sources writer retry-effects <source> --parked-pushes`. Three narrower gaps are closed too: in a managed root below the repository's top level, a commit changing that root's own `.gbrain-scan-allow` is held like one at the top level, and its path globs match paths relative to that root; a strict (canonical: git) source's commit whose files a Git clean filter changed is scanned instead of trusted (it is still pushed when the scan finds nothing); and Git replace refs no longer change what a page-write commit holds.
+A managed worktree now scans every push it makes for secrets, including the generated-page commits the dream cycle writes through and a push handed over from a busy publish lock, which used to go out unscanned. Only the commits the remote lacks are scanned, never history it already holds. A credential in an unpushed commit, or a false positive there, holds the push with `publish_secret_found` naming the file, line and rule, never the value; remove it from the commit or add its fingerprint to `.gbrain-scan-allow`, then run `gbrain sources writer retry-effects <source> --parked-pushes`. Three narrower gaps are closed too: in a managed root below the repository's top level, a commit changing that root's own `.gbrain-scan-allow` is held like one at the top level, and its path globs match paths relative to that root; a strict (canonical: git) source's commit whose files a Git clean filter changed is scanned instead of trusted (it is still pushed when the scan finds nothing), and a strict-source commit made before this release that is still unpushed is scanned once on its push; and Git replace refs no longer change what a page-write commit holds.