Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript

v0.60.512.0: restamp after #8012 (.511)

garrytan9386aa94597a
diff --git a/VERSION b/VERSION
index 14bb881bc3..1130aa88cf 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-0.60.511.0
+0.60.512.0
diff --git a/package.json b/package.json
index 880c0d3df9..d2db1cba03 100644
--- a/package.json
+++ b/package.json
@@ -246,7 +246,7 @@
"bun": ">=1.4.4"
},
"license": "MIT",
- "version": "0.60.511.0",
+ "version": "0.60.512.0",
"overrides": {
"@ai-sdk/provider-utils": "4.0.56",
"@hono/node-server": "^2.0.5",
diff --git a/src/core/behavior-change-notice.ts b/src/core/behavior-change-notice.ts
index 49a6c5c80a..f5f90d229c 100644
--- a/src/core/behavior-change-notice.ts
+++ b/src/core/behavior-change-notice.ts
@@ -1248,7 +1248,7 @@ export const BEHAVIOR_CHANGES: ReadonlyArray<{ since: string; text: ChangeText;
{ since: '0.60.427.0', text: 'More gbrain state follows GBRAIN_HOME: feature offers (`feature-offers.json`), the upgrade state and error log, `mounts.json` and the mounts cache, the brain-pull log (including the log paths a newly installed launchd pull job writes), the default supervisor pid file, skillopt captures, the transcript harvest pattern file, notability eval files and the greenfield import audit directory now live under `<GBRAIN_HOME>/.gbrain` when GBRAIN_HOME is set. Before, they were written under `$HOME/.gbrain` whatever GBRAIN_HOME said. With GBRAIN_HOME unset nothing moves. A host that sets GBRAIN_HOME keeps its old copies under `$HOME/.gbrain`: move them by hand if you want the old offers, mounts or upgrade history, and restart a supervisor that was started before the upgrade so `gbrain jobs supervisor status` finds its pid file.' },
// GBRA-175 (stable channel, upgrade restarts every process). `since` is stamped at the merge slot.
{ since: '0.60.428.0', id: 'upgrade_restarts_7245', text: '`gbrain upgrade` now restarts every gbrain process this brain runs on the host onto the new build (serve and autopilot through their installed services, the jobs supervisor and its worker with `gbrain jobs supervisor stop` then `start --detach`) and verifies that they all report one build and that the warm CLI socket accepts it. Before installing anything it refuses with `restart_refused` (exit 3) when a process cannot be restarted automatically: a serve or worker started by hand, an autopilot without its service, a running sync, or an MCP server an agent harness started (rerun with `--stop-mcp` to stop those; reconnect gbrain in each harness afterwards). `--no-restart` installs without restarting; `gbrain upgrade --restart-only` restarts onto the installed build (`--dry-run` previews). The autopilot `--swap-only` channel is unchanged.' },
- { since: '0.60.511.0', id: 'autopilot_restarts_serve_7475', text: 'With `self_upgrade.mode auto`, the autopilot that relaunches after a self-upgrade now restarts the serve your installed serve service runs (`com.gbrain.serve` under launchd, `gbrain-serve.service` under systemd) when that serve is still on the old build, and verifies it came back on the new one. It runs once per relaunch, in quiet hours, when the brain is idle, and audits as `restart_serve`. A serve started by hand or from another install is never restarted: doctor `runtime_build_skew` keeps failing with `gbrain upgrade --restart-only` as its fix.' },
+ { since: '0.60.512.0', id: 'autopilot_restarts_serve_7475', text: 'With `self_upgrade.mode auto`, the autopilot that relaunches after a self-upgrade now restarts the serve your installed serve service runs (`com.gbrain.serve` under launchd, `gbrain-serve.service` under systemd) when that serve is still on the old build, and verifies it came back on the new one. It runs once per relaunch, in quiet hours, when the brain is idle, and audits as `restart_serve`. A serve started by hand or from another install is never restarted: doctor `runtime_build_skew` keeps failing with `gbrain upgrade --restart-only` as its fix.' },
{ since: '0.60.428.0', id: 'runtime_build_skew_fails_7245', text: 'doctor `runtime_build_skew` now fails (was a warning) when two or more gbrain builds run on this host, and its fix asks the user before running `gbrain upgrade --restart-only`; one process older than its install alone still warns. New release channel: `gbrain upgrade --channel stable` or `gbrain config set self_upgrade.channel stable` installs only releases a maintainer promoted after the production-shaped soak passed on their exact tree, and the update checks then offer only that release; the default channel (`latest`) is unchanged.' },
{ since: '0.60.430.0', text: 'In a managed canonical worktree, `gbrain git commit-push -m <msg> -- <paths>` now commits the named paths there (outcome `committed_local`, exit 0) instead of refusing `writer_coordinator_required`. It takes the commit lock and commits only those paths: it never fetches, merges, pushes or moves the checkout, so the persistence owner stays the only publisher; the owner\'s next Git publish, or `gbrain git commit-push --push-only --keep-checkout`, pushes the commit. --pending, --branch, --resolve, --expect-remote and --allow-outside-source-root are refused there (`commit_paths_invalid`).' },
{ since: '0.60.430.0', text: 'The `refresh_diverged` refusal of `gbrain sources refresh` now counts the checkout\'s local commits and its fix is `gbrain git commit-push --push-only --keep-checkout --path <root> --json` (actor user, ask_user): it merges the upstream in memory, refuses on a conflict, pushes the merge and never moves the checkout, after which the refresh fast-forwards. It used to suggest reconciling in a separate clone or recloning, which drops the local commits.' },