feat: retain qualified release operation before publication - #153
Merged
Conversation
pcvantol
force-pushed
the
codex/ep-release-prepublication-operation-v1
branch
from
September 9, 2026 13:47
e2ad7b7 to
cc1bc34
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
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.
Problem
EP persisted its release operation only after PyPI publication, leaving no exact operation record bound before registry side effects and retaining conflicting release-branch documentation.
Change
Qualification now persists a deterministic QUALIFIED release operation with the exact protected-main SHA and wheel/sdist digests before publication. The publisher and PyPI readback jobs verify that record before proceeding. Release documentation and NFR wording now consistently describe main-first publication and call remaining cross-run recovery gaps out explicitly.
Validation
PYTHONPATH=src python3 -m unittest tests.engineering.test_release_operation tests.engineering.test_engineering_platform_nfrNo release action
This changes source and workflow only; it does not publish a version or change a local installation.