mirror of
https://github.com/openclaw/openclaw.git
synced 2026-05-06 08:10:44 +00:00
test(update): cover authenticated restart updates
This commit is contained in:
@@ -141,11 +141,13 @@ the maintainer-only release runbook.
|
||||
`telegram_mode=mock-openai` or `telegram_mode=live-frontier`. When the
|
||||
selected Docker lanes include `published-upgrade-survivor`, the package
|
||||
artifact is the candidate and `published_upgrade_survivor_baseline` selects
|
||||
the published baseline.
|
||||
the published baseline. `update-restart-auth` uses the candidate package as
|
||||
both the installed CLI and the package-under-test so it exercises the
|
||||
candidate update command's managed restart path.
|
||||
Example: `gh workflow run package-acceptance.yml --ref main -f workflow_ref=main -f source=npm -f package_spec=openclaw@beta -f suite_profile=product -f published_upgrade_survivor_baseline=openclaw@2026.4.26 -f telegram_mode=mock-openai`
|
||||
Common profiles:
|
||||
- `smoke`: install/channel/agent, gateway network, and config reload lanes
|
||||
- `package`: artifact-native package/update/plugin lanes without OpenWebUI or live ClawHub
|
||||
- `package`: artifact-native package/update/restart/plugin lanes without OpenWebUI or live ClawHub
|
||||
- `product`: package profile plus MCP channels, cron/subagent cleanup,
|
||||
OpenAI web search, and OpenWebUI
|
||||
- `full`: Docker release-path chunks with OpenWebUI
|
||||
@@ -486,11 +488,12 @@ Supported candidate sources:
|
||||
|
||||
`OpenClaw Release Checks` runs Package Acceptance with `source=artifact`, the
|
||||
prepared release package artifact, `suite_profile=custom`,
|
||||
`docker_lanes=doctor-switch update-channel-switch upgrade-survivor published-upgrade-survivor plugins-offline plugin-update`,
|
||||
`telegram_mode=mock-openai`. Package Acceptance keeps migration, update, stale
|
||||
plugin dependency cleanup, offline plugin fixtures, plugin update, and Telegram
|
||||
package QA against the same resolved tarball. Blocking release checks use the
|
||||
default latest published package baseline; `run_release_soak=true` or
|
||||
`docker_lanes=doctor-switch update-channel-switch upgrade-survivor published-upgrade-survivor update-restart-auth plugins-offline plugin-update`,
|
||||
`telegram_mode=mock-openai`. Package Acceptance keeps migration, update,
|
||||
configured-auth update restart, stale plugin dependency cleanup, offline plugin
|
||||
fixtures, plugin update, and Telegram package QA against the same resolved
|
||||
tarball. Blocking release checks use the default latest published package
|
||||
baseline; `run_release_soak=true` or
|
||||
`release_profile=full` expands to every stable npm-published baseline from
|
||||
`2026.4.23` through `latest` plus reported-issue fixtures. Use
|
||||
Package Acceptance with `source=npm` for an already shipped candidate, or
|
||||
@@ -536,8 +539,8 @@ Common package profiles:
|
||||
|
||||
- `smoke`: quick package install/channel/agent, gateway network, and config
|
||||
reload lanes
|
||||
- `package`: install/update/plugin package contracts without live ClawHub; this is the release-check
|
||||
default
|
||||
- `package`: install/update/restart/plugin package contracts without live
|
||||
ClawHub; this is the release-check default
|
||||
- `product`: `package` plus MCP channels, cron/subagent cleanup, OpenAI web
|
||||
search, and OpenWebUI
|
||||
- `full`: Docker release-path chunks with OpenWebUI
|
||||
|
||||
Reference in New Issue
Block a user