Repository navigation
馃懛 ci(release): gate tagged publishing - #276
Merged
Merged
Conversation
Backfill the tagged history and require PR news in the aggregate. Commit release notes before an App pushes the tag, then check the tag and built distributions before publishing to PyPI.
gaborbernat
added
enhancement
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 tags currently publish to PyPI without a committed changelog entry or a check that the built distributions match the tag. The repository also lacks a single required status covering its test matrix and news policy.
This PR backfills the tagged history and removes generated release-note comments from the changelog. Contributor PRs require a nonempty fragment unless labeled
skip news. A preparation workflow commits the next changelog entry on main with a repository-only App, then pushes a tag that starts the existing PyPI trusted-publishing workflow. The build checks the changelog and distribution versions before publication.A pytest-dev organization admin must create and install the repository-only App, set
RELEASE_APP_CLIENT_IDandRELEASE_APP_PRIVATE_KEYinrelease-auth, and protect main and release tags. RequireRequired checks pass; allow admins and the App to bypass, with no review-approval requirement.