test: add update migration package gate · openclaw/openclaw@682e055

Recent Commits to openclaw:main

steipete · 2026-05-02 · via Recent Commits to openclaw:main

Original file line number	Diff line number	Diff line change
`@@ -34,17 +34,17 @@ on:`
`34`	`34`	`default: 1`
`35`	`35`	`type: number`
`36`	`36`	`published_upgrade_survivor_baseline:`
`37`		`-description: Published OpenClaw package baseline for the published-upgrade-survivor Docker lane`
	`37`	`+description: Published OpenClaw package baseline for the published-upgrade-survivor/update-migration Docker lane`
`38`	`38`	`required: false`
`39`	`39`	`default: openclaw@latest`
`40`	`40`	`type: string`
`41`	`41`	`published_upgrade_survivor_baselines:`
`42`		`-description: Optional exact baseline list for published-upgrade-survivor lane expansion`
	`42`	`+description: Optional exact baseline list for published-upgrade-survivor/update-migration lane expansion`
`43`	`43`	`required: false`
`44`	`44`	`default: ""`
`45`	`45`	`type: string`
`46`	`46`	`published_upgrade_survivor_scenarios:`
`47`		`-description: Optional scenario list for published-upgrade-survivor lane expansion`
	`47`	`+description: Optional scenario list for published-upgrade-survivor/update-migration lane expansion`
`48`	`48`	`required: false`
`49`	`49`	`default: ""`
`50`	`50`	`type: string`
`@@ -129,17 +129,17 @@ on:`
`129`	`129`	`default: 1`
`130`	`130`	`type: number`
`131`	`131`	`published_upgrade_survivor_baseline:`
`132`		`-description: Published OpenClaw package baseline for the published-upgrade-survivor Docker lane`
	`132`	`+description: Published OpenClaw package baseline for the published-upgrade-survivor/update-migration Docker lane`
`133`	`133`	`required: false`
`134`	`134`	`default: openclaw@latest`
`135`	`135`	`type: string`
`136`	`136`	`published_upgrade_survivor_baselines:`
`137`		`-description: Optional exact baseline list for published-upgrade-survivor lane expansion`
	`137`	`+description: Optional exact baseline list for published-upgrade-survivor/update-migration lane expansion`
`138`	`138`	`required: false`
`139`	`139`	`default: ""`
`140`	`140`	`type: string`
`141`	`141`	`published_upgrade_survivor_scenarios:`
`142`		`-description: Optional scenario list for published-upgrade-survivor lane expansion`
	`142`	`+description: Optional scenario list for published-upgrade-survivor/update-migration lane expansion`
`143`	`143`	`required: false`
`144`	`144`	`default: ""`
`145`	`145`	`type: string`

Original file line number	Diff line number	Diff line change
`@@ -70,12 +70,12 @@ on:`
`70`	`70`	`default: openclaw@latest`
`71`	`71`	`type: string`
`72`	`72`	`published_upgrade_survivor_baselines:`
`73`		`-description: Optional baseline list for published-upgrade-survivor; use release-history for last 6 plus key legacy releases`
	`73`	`+description: Optional baseline list for published-upgrade-survivor/update-migration; use release-history or all-since-2026.4.23`
`74`	`74`	`required: false`
`75`	`75`	`default: ""`
`76`	`76`	`type: string`
`77`	`77`	`published_upgrade_survivor_scenarios:`
`78`		`-description: Optional scenario list for published-upgrade-survivor; use reported-issues for known upgrade failure shapes`
	`78`	`+description: Optional scenario list for published-upgrade-survivor/update-migration; use reported-issues for known upgrade failure shapes`
`79`	`79`	`required: false`
`80`	`80`	`default: ""`
`81`	`81`	`type: string`
`@@ -150,12 +150,12 @@ on:`
`150`	`150`	`default: openclaw@latest`
`151`	`151`	`type: string`
`152`	`152`	`published_upgrade_survivor_baselines:`
`153`		`-description: Optional baseline list for published-upgrade-survivor; use release-history for last 6 plus key legacy releases`
	`153`	`+description: Optional baseline list for published-upgrade-survivor/update-migration; use release-history or all-since-2026.4.23`
`154`	`154`	`required: false`
`155`	`155`	`default: ""`
`156`	`156`	`type: string`
`157`	`157`	`published_upgrade_survivor_scenarios:`
`158`		`-description: Optional scenario list for published-upgrade-survivor; use reported-issues for known upgrade failure shapes`
	`158`	`+description: Optional scenario list for published-upgrade-survivor/update-migration; use reported-issues for known upgrade failure shapes`
`159`	`159`	`required: false`
`160`	`160`	`default: ""`
`161`	`161`	`type: string`
`@@ -442,7 +442,7 @@ jobs:`
`442`	`442`	`fi`
`443`	`443`	`releases_json=""`
`444`	`444`	`npm_versions_json=""`
`445`		`- if [[ "$REQUESTED_BASELINES" == "release-history" ]]; then`
	`445`	`+ if [[ "$REQUESTED_BASELINES" == "release-history" \|\| "$REQUESTED_BASELINES" == "all-since-" ]]; then`
`446`	`446`	`releases_json=".artifacts/package-candidate-input/openclaw-releases.json"`
`447`	`447`	`npm_versions_json=".artifacts/package-candidate-input/openclaw-npm-versions.json"`
`448`	`448`	`mkdir -p "$(dirname "$releases_json")"`

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,46 @@`
	`1`	`+name: Update Migration`
	`2`	`+`
	`3`	`+on:`
	`4`	`+workflow_dispatch:`
	`5`	`+inputs:`
	`6`	`+workflow_ref:`
	`7`	`+description: Trusted workflow/harness ref`
	`8`	`+default: main`
	`9`	`+required: true`
	`10`	`+type: string`
	`11`	`+package_ref:`
	`12`	`+description: Branch, tag, or SHA to package as the update target`
	`13`	`+default: main`
	`14`	`+required: true`
	`15`	`+type: string`
	`16`	`+baselines:`
	`17`	`+description: Published baselines to migrate; use all-since-2026.4.23 for full coverage`
	`18`	`+default: all-since-2026.4.23`
	`19`	`+required: true`
	`20`	`+type: string`
	`21`	`+scenarios:`
	`22`	`+description: Update survivor scenarios`
	`23`	`+default: plugin-deps-cleanup`
	`24`	`+required: true`
	`25`	`+type: string`
	`26`	`+`
	`27`	`+permissions:`
	`28`	`+actions: read`
	`29`	`+contents: read`
	`30`	`+packages: write`
	`31`	`+pull-requests: read`
	`32`	`+`
	`33`	`+jobs:`
	`34`	`+update_migration:`
	`35`	`+name: Update migration matrix`
	`36`	`+uses: ./.github/workflows/package-acceptance.yml`
	`37`	`+with:`
	`38`	`+workflow_ref: ${{ inputs.workflow_ref }}`
	`39`	`+source: ref`
	`40`	`+package_ref: ${{ inputs.package_ref }}`
	`41`	`+suite_profile: custom`
	`42`	`+docker_lanes: update-migration`
	`43`	`+published_upgrade_survivor_baselines: ${{ inputs.baselines }}`
	`44`	`+published_upgrade_survivor_scenarios: ${{ inputs.scenarios }}`
	`45`	`+telegram_mode: none`
	`46`	`+secrets: inherit`

Original file line number	Diff line number	Diff line change
`@@ -192,7 +192,7 @@ For the dedicated update and plugin testing policy, including local commands,`
`192`	`192`	`Docker lanes, Package Acceptance inputs, release defaults, and failure triage,`
`193`	`193`	`see [Testing updates and plugins](/help/testing-updates-plugins).`
`194`	`194`
`195`		-Release checks call 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'`, `published_upgrade_survivor_baselines=release-history`, `published_upgrade_survivor_scenarios=reported-issues`, and `telegram_mode=mock-openai`. This keeps package migration, update, stale-plugin-dependency cleanup, offline plugin, plugin-update, and Telegram proof on the same resolved package tarball. Cross-OS release checks still cover OS-specific onboarding, installer, and platform behavior; package/update product validation should start with Package Acceptance. The `published-upgrade-survivor` Docker lane validates one published package baseline per run. In Package Acceptance, the resolved `package-under-test` tarball is always the candidate and `published_upgrade_survivor_baseline` selects the fallback published baseline, defaulting to `openclaw@latest`; failed-lane rerun commands preserve that baseline. Set `published_upgrade_survivor_baselines=release-history` to expand the lane across a deduped history matrix: the latest six stable releases, `2026.4.23`, and the latest stable release before `2026-03-15`. Set `published_upgrade_survivor_scenarios=reported-issues` to expand the same baselines across issue-shaped fixtures for Feishu config, preserved bootstrap/persona files, tilde log paths, and stale legacy plugin dependency roots. Local aggregate runs can pass exact package specs with `OPENCLAW_UPGRADE_SURVIVOR_BASELINE_SPECS`, keep a single lane with `OPENCLAW_UPGRADE_SURVIVOR_BASELINE_SPEC` such as `openclaw@2026.4.15`, or set `OPENCLAW_UPGRADE_SURVIVOR_SCENARIOS` for the scenario matrix. The published lane configures the baseline with a baked `openclaw config set` command recipe, records recipe steps in `summary.json`, and probes `/healthz`, `/readyz`, plus RPC status after Gateway start. The Windows packaged and installer fresh lanes also verify that an installed package can import a browser-control override from a raw absolute Windows path. The OpenAI cross-OS agent-turn smoke defaults to `OPENCLAW_CROSS_OS_OPENAI_MODEL` when set, otherwise `openai/gpt-5.5`, so the install and gateway proof stays on the preferred GPT-5 test model.
	`195`	+Release checks call 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'`, `published_upgrade_survivor_baselines=release-history`, `published_upgrade_survivor_scenarios=reported-issues`, and `telegram_mode=mock-openai`. This keeps package migration, update, stale-plugin-dependency cleanup, offline plugin, plugin-update, and Telegram proof on the same resolved package tarball. Cross-OS release checks still cover OS-specific onboarding, installer, and platform behavior; package/update product validation should start with Package Acceptance. The `published-upgrade-survivor` Docker lane validates one published package baseline per run. In Package Acceptance, the resolved `package-under-test` tarball is always the candidate and `published_upgrade_survivor_baseline` selects the fallback published baseline, defaulting to `openclaw@latest`; failed-lane rerun commands preserve that baseline. Set `published_upgrade_survivor_baselines=release-history` to expand the lane across a deduped history matrix: the latest six stable releases, `2026.4.23`, and the latest stable release before `2026-03-15`. Set `published_upgrade_survivor_scenarios=reported-issues` to expand the same baselines across issue-shaped fixtures for Feishu config, preserved bootstrap/persona files, tilde log paths, and stale legacy plugin dependency roots. The separate `Update Migration` workflow uses the `update-migration` Docker lane with `all-since-2026.4.23` and `plugin-deps-cleanup` when the question is exhaustive published update cleanup, not normal Full Release CI breadth. Local aggregate runs can pass exact package specs with `OPENCLAW_UPGRADE_SURVIVOR_BASELINE_SPECS`, keep a single lane with `OPENCLAW_UPGRADE_SURVIVOR_BASELINE_SPEC` such as `openclaw@2026.4.15`, or set `OPENCLAW_UPGRADE_SURVIVOR_SCENARIOS` for the scenario matrix. The published lane configures the baseline with a baked `openclaw config set` command recipe, records recipe steps in `summary.json`, and probes `/healthz`, `/readyz`, plus RPC status after Gateway start. The Windows packaged and installer fresh lanes also verify that an installed package can import a browser-control override from a raw absolute Windows path. The OpenAI cross-OS agent-turn smoke defaults to `OPENCLAW_CROSS_OS_OPENAI_MODEL` when set, otherwise `openai/gpt-5.5`, so the install and gateway proof stays on the preferred GPT-5 test model.
`196`	`196`
`197`	`197`	`### Legacy compatibility windows`
`198`	`198`

Original file line number	Diff line number	Diff line change
`@@ -77,6 +77,7 @@ pnpm test:docker:plugins`
`77`	`77`	`pnpm test:docker:plugin-update`
`78`	`78`	`pnpm test:docker:upgrade-survivor`
`79`	`79`	`pnpm test:docker:published-upgrade-survivor`
	`80`	`+pnpm test:docker:update-migration`
`80`	`81`	```
`81`	`82`
`82`	`83`	`Important lanes:`
`@@ -95,6 +96,12 @@ Important lanes:`
`95`	`96`	configures it through a baked `openclaw config set` recipe, updates it to the
`96`	`97`	`candidate tarball, runs doctor, checks legacy cleanup, starts the Gateway, and`
`97`	`98`	probes `/healthz`, `/readyz`, and RPC status.
	`99`	+- `test:docker:update-migration` is the cleanup-heavy published-update lane. It
	`100`	`+ starts from a configured Discord/Telegram-style user state, runs baseline`
	`101`	`+ doctor so configured plugin dependencies have a chance to materialize, seeds`
	`102`	`+ legacy plugin dependency debris for a configured packaged plugin, updates to`
	`103`	`+ the candidate tarball, and requires post-update doctor to remove the legacy`
	`104`	`+ dependency roots.`
`98`	`105`
`99`	`106`	`Useful published-upgrade survivor variants:`
`100`	`107`
`@@ -109,10 +116,24 @@ pnpm test:docker:published-upgrade-survivor`
`109`	`116`	```
`110`	`117`
`111`	`118`	Available scenarios are `base`, `feishu-channel`, `bootstrap-persona`,
`112`		-`tilde-log-path`, and `versioned-runtime-deps`. In aggregate runs,
	`119`	+`plugin-deps-cleanup`, `tilde-log-path`, and `versioned-runtime-deps`. In aggregate runs,
`113`	`120`	`OPENCLAW_UPGRADE_SURVIVOR_SCENARIOS=reported-issues` expands to all reported
`114`	`121`	`issue-shaped scenarios.`
`115`	`122`
	`123`	`+Full update migration is intentionally separate from Full Release CI. Use the`
	`124`	+manual `Update Migration` workflow when the release question is "can every
	`125`	`+published stable release from 2026.4.23 onward update to this candidate and`
	`126`	`+clean up plugin dependency debris?":`
	`127`	`+`
	`128`	+```bash
	`129`	`+gh workflow run update-migration.yml \`
	`130`	`+ --ref main \`
	`131`	`+ -f workflow_ref=main \`
	`132`	`+ -f package_ref=main \`
	`133`	`+ -f baselines=all-since-2026.4.23 \`
	`134`	`+ -f scenarios=plugin-deps-cleanup`
	`135`	+```
	`136`	`+`
`116`	`137`	`## Package Acceptance`
`117`	`138`
`118`	`139`	`Package Acceptance is the GitHub-native package gate. It resolves one candidate`
`@@ -148,6 +169,11 @@ This keeps package migration, update channel switching, stale plugin dependency`
`148`	`169`	`cleanup, offline plugin coverage, plugin update behavior, and Telegram package`
`149`	`170`	`QA on the same resolved artifact.`
`150`	`171`
	`172`	+`release-history` is a bounded release-check sample: latest six stable releases,
	`173`	+`2026.4.23`, and one older pre-date anchor. For exhaustive published update
	`174`	+migration coverage, use `all-since-2026.4.23` in the separate Update Migration
	`175`	`+workflow instead of Full Release CI.`
	`176`	`+`
`151`	`177`	`Run a package profile manually when validating a candidate before release:`
`152`	`178`
`153`	`179`	```bash

Original file line number	Diff line number	Diff line change
`@@ -445,6 +445,8 @@ The canonical checklist for update and plugin validation is`
`445`	`445`	`[Testing updates and plugins](/help/testing-updates-plugins). Use it when`
`446`	`446`	`deciding which local, Docker, Package Acceptance, or release-check lane proves a`
`447`	`447`	`plugin install/update, doctor cleanup, or published-package migration change.`
	`448`	+Exhaustive published update migration from every stable `2026.4.23+` package is
	`449`	+a separate manual `Update Migration` workflow, not part of Full Release CI.
`448`	`450`
`449`	`451`	`Legacy package-acceptance leniency is intentionally time boxed. Packages through`
`450`	`452`	`2026.4.25` may use the compatibility path for metadata gaps already published

Original file line number	Diff line number	Diff line change
`@@ -45,6 +45,7 @@ title: "Tests"`
`45`	`45`	- `pnpm test:docker:mcp-channels`: Starts a seeded Gateway container and a second client container that spawns `openclaw mcp serve`, then verifies routed conversation discovery, transcript reads, attachment metadata, live event queue behavior, outbound send routing, and Claude-style channel + permission notifications over the real stdio bridge. The Claude notification assertion reads the raw stdio MCP frames directly so the smoke reflects what the bridge actually emits.
`46`	`46`	- `pnpm test:docker:upgrade-survivor`: Installs the packed OpenClaw tarball over a dirty old-user fixture, runs package update plus non-interactive doctor without live provider or channel keys, then starts a loopback Gateway and checks that agents, channel config, plugin allowlists, workspace/session files, stale legacy plugin dependency state, startup, and RPC status survive.
`47`	`47`	- `pnpm test:docker:published-upgrade-survivor`: Installs `openclaw@latest` by default, seeds realistic existing-user files without live provider or channel keys, configures that baseline with a baked `openclaw config set` command recipe, updates that published install to the packed OpenClaw tarball, runs non-interactive doctor, writes `.artifacts/upgrade-survivor/summary.json`, then starts a loopback Gateway and checks that configured intents, workspace/session files, stale plugin config and legacy dependency state, startup, `/healthz`, `/readyz`, and RPC status survive or repair cleanly. Override one baseline with `OPENCLAW_UPGRADE_SURVIVOR_BASELINE_SPEC`, expand an exact matrix with `OPENCLAW_UPGRADE_SURVIVOR_BASELINE_SPECS`, or add scenario fixtures with `OPENCLAW_UPGRADE_SURVIVOR_SCENARIOS=reported-issues`; Package Acceptance exposes those as `published_upgrade_survivor_baseline`, `published_upgrade_survivor_baselines`, and `published_upgrade_survivor_scenarios`.
	`48`	+- `pnpm test:docker:update-migration`: Runs the published-upgrade survivor harness in the cleanup-heavy `plugin-deps-cleanup` scenario, starting at `openclaw@2026.4.23` by default. The separate `Update Migration` workflow expands this lane with `baselines=all-since-2026.4.23` so every stable published package from `.23` onward updates to the candidate and proves configured-plugin dependency cleanup outside Full Release CI.
`48`	`49`
`49`	`50`	`## Local PR gate`
`50`	`51`

Original file line number	Diff line number	Diff line change
`@@ -1518,6 +1518,7 @@`
`1518`	`1518`	`"test:docker:session-runtime-context": "bash scripts/e2e/session-runtime-context-docker.sh",`
`1519`	`1519`	`"test:docker:timings": "node scripts/docker-e2e-timings.mjs",`
`1520`	`1520`	`"test:docker:update-channel-switch": "bash scripts/e2e/update-channel-switch-docker.sh",`
	`1521`	`+"test:docker:update-migration": "env OPENCLAW_UPGRADE_SURVIVOR_PUBLISHED_BASELINE=1 OPENCLAW_UPGRADE_SURVIVOR_BASELINE_SPEC=${OPENCLAW_UPGRADE_SURVIVOR_BASELINE_SPEC:-openclaw@2026.4.23} OPENCLAW_UPGRADE_SURVIVOR_SCENARIO=${OPENCLAW_UPGRADE_SURVIVOR_SCENARIO:-plugin-deps-cleanup} bash scripts/e2e/upgrade-survivor-docker.sh",`
`1521`	`1522`	`"test:docker:upgrade-survivor": "bash scripts/e2e/upgrade-survivor-docker.sh",`
`1522`	`1523`	`"test:e2e": "node scripts/run-vitest.mjs run --config test/vitest/vitest.e2e.config.ts",`
`1523`	`1524`	`"test:e2e:openshell": "OPENCLAW_E2E_OPENSHELL=1 node scripts/run-vitest.mjs run --config test/vitest/vitest.e2e.config.ts extensions/openshell/src/backend.e2e.test.ts",`

Original file line number	Diff line number	Diff line change
`@@ -6,6 +6,7 @@ const SCENARIOS = new Set([`
`6`	`6`	`"base",`
`7`	`7`	`"feishu-channel",`
`8`	`8`	`"bootstrap-persona",`
	`9`	`+"plugin-deps-cleanup",`
`9`	`10`	`"tilde-log-path",`
`10`	`11`	`"versioned-runtime-deps",`
`11`	`12`	`]);`

此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。原文来自 — 版权归原作者所有。

推荐订阅源

Recent Commits to openclaw:main