Repository navigation
馃懛 ci: publish release after PyPI - #153
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
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.
Release preparation currently creates a GitHub Release before PyPI accepts the distributions. A failed package upload can leave the GitHub Release announcing a version that PyPI does not have.
The tag workflow creates the GitHub Release after PyPI succeeds, using that tag's changelog section, a PyPI link, and a comparison with the previous tag. It renders the changelog's RST roles as readable Markdown. The protected commit and tag push still uses the repository-scoped App token; only the GitHub Release job receives GitHub write access.
The tracked changelog now includes 1.5.2 and 1.6.3. Fragments for fixes already shipped in 1.6.3 are removed so they do not appear again in the next release.