Fix release publishing, direct pushes, and macOS 3.14 wheels - #431
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.
Summary
Fix release run 35527600540 and simplify future releases:
uv publishinstead of deprecatedmaturin upload, using the existingPYPI_API_TOKENand downloaded artifacts indist/.main, create a version commit with[skip ci]and build every package from that exact SHA. Do not open a release PR or run redundant push/PR CI for the version commit. Normal development PR checks remain unchanged.mainand create the release tag without force. Identical retries succeed; conflicting tags or concurrent changes tomainare rejected. Checkmainbefore publishing as well.Required setup
Add repository secret
RELEASE_GITHUB_TOKEN: a GitHub token with repository contents write access whose actor is permitted to bypassmain's required checks. The ordinaryGITHUB_TOKENcannot bypass them. The workflow fails before preparing or publishing a release if this secret is absent. Token presence is checked locally; GitHub authorization must still be configured correctly.This does not change repository protection or reuse local credentials. Previously approved required-check name repairs remain in place. Keep
mainunchanged during a release; a race after the pre-publication check will safely reject the final push rather than overwrite work. Git and PyPI cannot be updated transactionally.[skip ci]suppresses push/PR workflows, not necessarily CodeQL default scanning or external integrations.Validation
main, and concurrent-main rejection without creating a tag. This exposed a shallow-checkout failure, fixed by fetching full history in the final job.uv publish --dry-run.The existing
v14.0.0tag is already correct and has not been moved. Upload of the missing 14.0.0 macOS wheel is a separate repair, currently waiting for a local PyPI credential; existing PyPI files will not be replaced.