ci: verify immutable eval release recovery - #303
Draft
abrichr wants to merge 5 commits into
Draft
Conversation
abrichr
force-pushed
the
codex/evals-release-lifecycle-contract
branch
from
August 27, 2026 16:52
b3dd56f to
5b56880
Compare
abrichr
force-pushed
the
codex/evals-release-lifecycle-contract
branch
from
August 27, 2026 17:00
5b56880 to
6225d0a
Compare
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
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.
PR #296 merged the base Release App and lifecycle workflow contract. This follow-up closes the immutable PyPI recovery gap that remained after that merge.
The release job checks any existing PyPI files before
skip-existingcan upload a missing file. It accepts an absent release or an exact subset. It refuses an extra file or a mismatch in the project, version, package type, yanked state, size, SHA-256 digest, source host, or downloaded bytes. A strict post-publication check then requires the complete wheel and source distribution.GitHub Release publication still uses a same-job, repository-scoped
openadapt-releasetoken. The workflow checks the App slug before the write. It also verifies the exact tag, App author, and immutable asset set.The Release, Lifecycle, and Docs App identities don't exist yet. The protected release environments and the Docs dispatcher also remain. This PR stays draft until those dependencies exist and a fresh Ops plan accepts the exact workflows.
Merging this PR won't create an App, environment, tag, release, admission, deployment, secret, or repository setting.
Checks
b3dd56fadb98fba442e8fab9df42fecb6b33612fef55e01ebe08382c9a05675d491dfbc297ed6d5e