Repository navigation
✨ feat(release): require versioned changelog - #324
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.
pyproject-apimoved its release notes to GitHub Releases after 1.6.1, leaving no tracked changelog for contributors or the release workflow to check. This restores a versioned history through 1.12.0 and links it from the documentation.Pull requests need a Towncrier fragment unless a maintainer applies
skip news. One aggregate status covers the test matrix and fragment check. Release preparation builds the changelog without a write credential; a separate job checks the patch before the repository App commits and tags it. After PyPI publication, the tag workflow creates a GitHub Release with that version's changelog section, a PyPI link, and a comparison with the previous tag.The App installation,
RELEASE_APP_CLIENT_IDandRELEASE_APP_PRIVATE_KEYinrelease-auth, and the branch and tag rulesets need to be configured before merge.