Repository navigation
馃懛 ci: publish GitHub Release after PyPI - #280
Merged
gaborbernat merged 1 commit intoOct 18, 2026
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.
PyPI publication can finish without a matching GitHub Release, leaving the published changelog and version diff hard to find from GitHub.
A separate job now creates the GitHub Release after PyPI succeeds. It uses the tagged changelog section, links the PyPI version and previous tag comparison, and holds GitHub write access only in that job. The release and preparation workflows pin the current uv and App-token actions.
All 25 existing GitHub Release bodies now use the same format. Four older PyPI versions have no repository tag and remain unresolved. The repository-only App remains responsible for protected release commits and tags. This internal workflow change uses
skip news.