fix(release): support frozen Codex validation#108343
Merged
Merged
Conversation
openclaw-barnacle
Bot
added
scripts
openclaw-barnacle
Bot
added
docs
Member
Author
|
Land-ready proof at exact head
The earlier red run |
Member
Author
|
Merged via squash.
|
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 16, 2026
* fix(release): support frozen Codex validation * fix(release): support frozen Codex validation * fix(release): support frozen Codex validation * fix(release): support frozen Codex validation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Problem This Solves
Full release validation uses a trusted current-main harness against an immutable release target. For frozen targets such as the v2026.6.11-based extended-stable candidate, the current harness was:
.release-harnessbefore building the target image, which accidentally added the current checkout to the Docker build context and produced an oversized image layer; andBoth failure modes occurred in Release Checks run 29413758794 attempt 3.
Why This Change Was Made
Keep the trusted release harness outside the target image build context by checking it out only after the image build and before artifact packing.
For the existing trusted
allow_frozen_target_scenario_omissionspath, inspect the frozen target's literal Codex fallback catalog before provider-suite setup. The generic Codex lane uses the newest model that target exposes, while GPT-5.6-only lanes are omitted only when the target predates the complete Sol/Luna capability cohort. Current targets and non-opted-in runs remain unchanged; incomplete capability markers fail closed.User Impact
Release validation can test old immutable targets with the release contract they actually support, without importing current runtime/model-catalog work into a maintenance release. Normal current-main validation still runs the full current Codex matrix.
Evidence
node scripts/run-vitest.mjs test/scripts/resolve-frozen-codex-live-suite.test.ts test/scripts/release-no-push-workflow.test.ts— 19 passed.node scripts/run-vitest.mjs test/scripts/package-acceptance-workflow.test.ts -- -t "runs Docker live harnesses from trusted helper scripts"— passed.actionlint .github/workflows/openclaw-live-and-e2e-checks-reusable.yml— passed.git diff --check— passed.$autoreview --mode local— clean, no accepted/actionable findings.The complete package-acceptance test file also exposed six existing Telegram child-summary failures outside this diff; the changed contract test passes independently.