@@ -78,6 +78,7 @@ pnpm test:docker:plugin-lifecycle-matrix
7878pnpm test:docker:plugin-update
7979pnpm test:docker:upgrade-survivor
8080pnpm test:docker:published-upgrade-survivor
81+pnpm test:docker:update-restart-auth
8182pnpm test:docker:update-migration
8283```
8384@@ -103,6 +104,10 @@ Important lanes:
103104 configures it through a baked `openclaw config set` recipe, updates it to the
104105 candidate tarball, runs doctor, checks legacy cleanup, starts the Gateway, and
105106 probes `/healthz`, `/readyz`, and RPC status.
107+- `test:docker:update-restart-auth` installs the candidate package, starts a
108+ managed token-auth Gateway, unsets caller gateway auth env for
109+`openclaw update --yes --json`, and requires the candidate update command to
110+ restart the Gateway before the normal probes.
106111- `test:docker:update-migration` is the cleanup-heavy published-update lane. It
107112 starts from a configured Discord/Telegram-style user state, runs baseline
108113 doctor so configured plugin dependencies have a chance to materialize, seeds
@@ -164,10 +169,10 @@ resolved release SHA. For post-publish proof, pass
164169`package_acceptance_package_spec=openclaw@YYYY.M.D` so the same upgrade matrix
165170targets the shipped npm package instead.
166171167-Release checks call Package Acceptance with the package/update/plugin set:
172+Release checks call Package Acceptance with the package/update/restart/plugin set:
168173169174```text
170-doctor-switch update-channel-switch upgrade-survivor published-upgrade-survivor plugins-offline plugin-update
175+doctor-switch update-channel-switch upgrade-survivor published-upgrade-survivor update-restart-auth plugins-offline plugin-update
171176```
172177173178When release soak is enabled, they also pass:
@@ -224,7 +229,7 @@ For release candidates, the default proof stack is:
2242291. `pnpm check:changed` and `pnpm test:changed` for source-level regressions.
2252302. `pnpm release:check` for package artifact integrity.
2262313. Package Acceptance `package` profile or the release-check custom package
227- lanes for install/update/plugin contracts.
232+ lanes for install/update/restart/plugin contracts.
2282334. Cross-OS release checks for OS-specific installer, onboarding, and platform
229234 behavior.
2302355. Live suites only when the changed surface touches provider or hosted-service
@@ -245,7 +250,8 @@ Compatibility leniency is narrow and time boxed:
245250 warning or skipping.
246251247252Do not add new startup migrations for these old shapes. Add or extend a doctor
248-repair, then prove it with `upgrade-survivor` or `published-upgrade-survivor`.
253+repair, then prove it with `upgrade-survivor`, `published-upgrade-survivor`, or
254+`update-restart-auth` when the update command owns the restart.
249255250256## Adding coverage
251257@@ -257,6 +263,7 @@ can fail for the right reason:
257263 checker test.
258264- CLI install/update behavior: Docker lane assertion or fixture.
259265- Published-release migration behavior: `published-upgrade-survivor` scenario.
266+- Update-owned restart behavior: `update-restart-auth`.
260267- Registry/package source behavior: `test:docker:plugins` fixture or ClawHub
261268 fixture server.
262269- Dependency layout or cleanup behavior: assert both runtime execution and the
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。