Repository navigation
Guard release deployment and tag successful uploads - #569
Merged
Merged
Conversation
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.
deploy.shcould publish from any checkout, ignored a requested version, and never tagged the release. It now deploys only the merged version from a cleanmain/mastermatching the live branch on origin, with no existing release tag. One sequence runs lint, tests, build and strict distribution checks, rechecks release state, uploads the exact wheel/sdist pair, then tags the original commit and pushes only the tag.--dry-runfollows that sequence through distribution checks and stops before publication. An optional version asserts the version already merged in the PR; it never creates a direct-main version bump. Each attempt preserves its original artifacts for verification and recovery. AGENTS.md, contributor setup and release instructions describe the same workflow. Version: 10.11.3.Validation:
./lint.sh,./test.sh(3,193 passed) andmkdocs build --strictall pass. The 13 argument/checkout/dry-run regressions fail against the previous script.twine check --strict.Closes #414. Historical tag/changelog reconstruction remains tracked in #411. The sibling-script inspection also uncovered and reproduced a dry-run mutation bug, filed as openvax/vaxrank#560.
Published 10.11.3 from merged commit
6f29cf8c5201189ae2803ad319aacca8053f7ddfusing the new script. Deployment reran all 3,193 tests, then uploaded both distributions and pushedv10.11.3to that same commit. The installed PyPI package passed an isolated import and CFTR baseline/cis annotation smoke test; both published SHA256 hashes match the preserved original files:552724b74e9a17423237289b4033c3b3ca919514d36f6fa955b64223ae42b9a99451d9d81c972c8116743a69bff8352a5c0398aefb486eaad106c2c916bdc65ePost-merge verification: Python matrix, documentation deployment.