default: 1

type: number

published_upgrade_survivor_baseline:

description: Published OpenClaw package baseline for the published-upgrade-survivor Docker lane

description: Published OpenClaw package baseline for the published-upgrade-survivor/update-migration Docker lane

required: false

default: openclaw@latest

type: string

published_upgrade_survivor_baselines:

description: Optional exact baseline list for published-upgrade-survivor lane expansion

description: Optional exact baseline list for published-upgrade-survivor/update-migration lane expansion

required: false

default: ""

type: string

published_upgrade_survivor_scenarios:

description: Optional scenario list for published-upgrade-survivor lane expansion

description: Optional scenario list for published-upgrade-survivor/update-migration lane expansion

required: false

default: ""

type: string

default: 1

type: number

published_upgrade_survivor_baseline:

description: Published OpenClaw package baseline for the published-upgrade-survivor Docker lane

description: Published OpenClaw package baseline for the published-upgrade-survivor/update-migration Docker lane

required: false

default: openclaw@latest

type: string

published_upgrade_survivor_baselines:

description: Optional exact baseline list for published-upgrade-survivor lane expansion

description: Optional exact baseline list for published-upgrade-survivor/update-migration lane expansion

required: false

default: ""

type: string

published_upgrade_survivor_scenarios:

description: Optional scenario list for published-upgrade-survivor lane expansion

description: Optional scenario list for published-upgrade-survivor/update-migration lane expansion

required: false

default: ""

type: string

default: openclaw@latest

type: string

published_upgrade_survivor_baselines:

description: Optional baseline list for published-upgrade-survivor; use release-history for last 6 plus key legacy releases

description: Optional baseline list for published-upgrade-survivor/update-migration; use release-history or all-since-2026.4.23

required: false

default: ""

type: string

published_upgrade_survivor_scenarios:

description: Optional scenario list for published-upgrade-survivor; use reported-issues for known upgrade failure shapes

description: Optional scenario list for published-upgrade-survivor/update-migration; use reported-issues for known upgrade failure shapes

required: false

default: ""

type: string

default: openclaw@latest

type: string

published_upgrade_survivor_baselines:

description: Optional baseline list for published-upgrade-survivor; use release-history for last 6 plus key legacy releases

description: Optional baseline list for published-upgrade-survivor/update-migration; use release-history or all-since-2026.4.23

required: false

default: ""

type: string

published_upgrade_survivor_scenarios:

description: Optional scenario list for published-upgrade-survivor; use reported-issues for known upgrade failure shapes

description: Optional scenario list for published-upgrade-survivor/update-migration; use reported-issues for known upgrade failure shapes

required: false

default: ""

type: string

fi

releases_json=""

npm_versions_json=""

if [[ "$REQUESTED_BASELINES" == *"release-history"* ]]; then

if [[ "$REQUESTED_BASELINES" == *"release-history"* || "$REQUESTED_BASELINES" == *"all-since-"* ]]; then

releases_json=".artifacts/package-candidate-input/openclaw-releases.json"

npm_versions_json=".artifacts/package-candidate-input/openclaw-npm-versions.json"

mkdir -p "$(dirname "$releases_json")"

name: Update Migration

on:

workflow_dispatch:

inputs:

workflow_ref:

description: Trusted workflow/harness ref

default: main

required: true

type: string

package_ref:

description: Branch, tag, or SHA to package as the update target

default: main

required: true

type: string

baselines:

description: Published baselines to migrate; use all-since-2026.4.23 for full coverage

default: all-since-2026.4.23

required: true

type: string

scenarios:

description: Update survivor scenarios

default: plugin-deps-cleanup

required: true

type: string

permissions:

actions: read

contents: read

packages: write

pull-requests: read

jobs:

update_migration:

name: Update migration matrix

uses: ./.github/workflows/package-acceptance.yml

with:

workflow_ref: ${{ inputs.workflow_ref }}

source: ref

package_ref: ${{ inputs.package_ref }}

suite_profile: custom

docker_lanes: update-migration

published_upgrade_survivor_baselines: ${{ inputs.baselines }}

published_upgrade_survivor_scenarios: ${{ inputs.scenarios }}

telegram_mode: none

secrets: inherit

Docker lanes, Package Acceptance inputs, release defaults, and failure triage,

see [Testing updates and plugins](/help/testing-updates-plugins).

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.

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.

### Legacy compatibility windows

pnpm test:docker:plugin-update

pnpm test:docker:upgrade-survivor

pnpm test:docker:published-upgrade-survivor

pnpm test:docker:update-migration

```

Important lanes:

configures it through a baked `openclaw config set` recipe, updates it to the

candidate tarball, runs doctor, checks legacy cleanup, starts the Gateway, and

probes `/healthz`, `/readyz`, and RPC status.

- `test:docker:update-migration` is the cleanup-heavy published-update lane. It

starts from a configured Discord/Telegram-style user state, runs baseline

doctor so configured plugin dependencies have a chance to materialize, seeds

legacy plugin dependency debris for a configured packaged plugin, updates to

the candidate tarball, and requires post-update doctor to remove the legacy

dependency roots.

Useful published-upgrade survivor variants:

```

Available scenarios are `base`, `feishu-channel`, `bootstrap-persona`,

`tilde-log-path`, and `versioned-runtime-deps`. In aggregate runs,

`plugin-deps-cleanup`, `tilde-log-path`, and `versioned-runtime-deps`. In aggregate runs,

`OPENCLAW_UPGRADE_SURVIVOR_SCENARIOS=reported-issues` expands to all reported

issue-shaped scenarios.

Full update migration is intentionally separate from Full Release CI. Use the

manual `Update Migration` workflow when the release question is "can every

published stable release from 2026.4.23 onward update to this candidate and

clean up plugin dependency debris?":

```bash

gh workflow run update-migration.yml \

--ref main \

-f workflow_ref=main \

-f package_ref=main \

-f baselines=all-since-2026.4.23 \

-f scenarios=plugin-deps-cleanup

```

## Package Acceptance

Package Acceptance is the GitHub-native package gate. It resolves one candidate

cleanup, offline plugin coverage, plugin update behavior, and Telegram package

QA on the same resolved artifact.

`release-history` is a bounded release-check sample: latest six stable releases,

`2026.4.23`, and one older pre-date anchor. For exhaustive published update

migration coverage, use `all-since-2026.4.23` in the separate Update Migration

workflow instead of Full Release CI.

Run a package profile manually when validating a candidate before release:

```bash

[Testing updates and plugins](/help/testing-updates-plugins). Use it when

deciding which local, Docker, Package Acceptance, or release-check lane proves a

plugin install/update, doctor cleanup, or published-package migration change.

Exhaustive published update migration from every stable `2026.4.23+` package is

a separate manual `Update Migration` workflow, not part of Full Release CI.

Legacy package-acceptance leniency is intentionally time boxed. Packages through

`2026.4.25` may use the compatibility path for metadata gaps already published

- `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.

- `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.

- `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`.

- `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.

## Local PR gate

"test:docker:session-runtime-context": "bash scripts/e2e/session-runtime-context-docker.sh",

"test:docker:timings": "node scripts/docker-e2e-timings.mjs",

"test:docker:update-channel-switch": "bash scripts/e2e/update-channel-switch-docker.sh",

"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",

"test:docker:upgrade-survivor": "bash scripts/e2e/upgrade-survivor-docker.sh",

"test:e2e": "node scripts/run-vitest.mjs run --config test/vitest/vitest.e2e.config.ts",

"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",

"base",

"feishu-channel",

"bootstrap-persona",

"plugin-deps-cleanup",

"tilde-log-path",

"versioned-runtime-deps",

]);