vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 09:10:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

ci: expand release upgrade baselines

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-02 19:45:52 +01:00
parent e18a383ff8
commit 4b4dfe429d
10 changed files with 85 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/help/testing-updates-plugins.md
View File

@@ -154,6 +154,11 @@ Candidate sources:
- `source=url`: validate an HTTPS tarball with required `package_sha256`.
- `source=artifact`: reuse a tarball uploaded by another Actions run.
Full Release Validation uses `source=artifact` by default, built from the
resolved release SHA. For post-publish proof, pass
`package_acceptance_package_spec=openclaw@YYYY.M.D` so the same upgrade matrix
targets the shipped npm package instead.
Release checks call Package Acceptance with the package/update/plugin set:
```text
@@ -163,7 +168,7 @@ doctor-switch update-channel-switch upgrade-survivor published-upgrade-survivor
They also pass:
```text
published_upgrade_survivor_baselines=release-history
published_upgrade_survivor_baselines=all-since-2026.4.23
published_upgrade_survivor_scenarios=reported-issues
telegram_mode=mock-openai
```
@@ -172,10 +177,11 @@ This keeps package migration, update channel switching, stale plugin dependency
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.
`all-since-2026.4.23` is the Full Release CI upgrade sample: every stable npm-published release from `2026.4.23` through `latest`. For exhaustive published
update migration coverage, use `all-since-2026.4.23` in the separate Update
Migration workflow instead of Full Release CI. `release-history` remains
available for manual wider sampling when you also want the legacy pre-date
anchor.
Run a package profile manually when validating a candidate before release:
@@ -186,7 +192,7 @@ gh workflow run package-acceptance.yml \
-f source=npm \
-f package_spec=openclaw@beta \
-f suite_profile=package \
-f published_upgrade_survivor_baselines=release-history \
-f published_upgrade_survivor_baselines=all-since-2026.4.23 \
-f published_upgrade_survivor_scenarios=reported-issues \
-f telegram_mode=mock-openai
```