Repository navigation
ci(release): tag and create the GitHub release when the PR merges - #783
Merged
Merged
Conversation
This was referenced Nov 12, 2026
When the release PR is merged to main, the same workflow builds and smoke-tests the wheel and the sdist of each released package, creates the tag and the GitHub release with the notes from the merged PR, and attaches the files. Uploading to PyPI stays with publish.yml for now.
masquare
force-pushed
the
ci/release-open-pr
branch
from
November 12, 2026 18:05
7b107df to
6f89304
Compare
masquare
force-pushed
the
ci/release-tag
branch
from
November 12, 2026 18:05
85c5c6c to
46c4cdd
Compare
masquare
marked this pull request as ready for review
November 13, 2026 15:32
Contributor
Author
|
Folded into #782. That PR now holds the release PR and the tag and GitHub release step, so the shared files are reviewed once. |
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.
Stack: automated per-package releases. Review the PRs in this order. Each PR shows only its own layer.
mainkeeps working after each merge. Nothing changes how packages are published until PR 4 deletespublish.yml.What this PR does
When the release PR is merged to
main, the same workflow builds the wheel and the sdist of each released package, smoke tests them, creates the tag, and creates the GitHub release with the files attached. The release notes are the text between the markers in the merged PR.Where to look
mainwhose commit message starts withchore(release):. A squash merge uses the PR title, so do not edit the title when you merge.released: finds the packages whose version the PR changed.smoke: imports each file in an isolated environment and makes sure that it records this commit.github-release: reads the notes from the merged PR and creates the tag and release. A re-run creates only what is missing.contents: writeandpull-requests: read, for this job only.Not in this PR
Uploading to TestPyPI and PyPI.
publish.ymlstill does that. PR 4 replaces it.Setup
None.
Testing
Run end to end in a private sandbox repository, with a real merge and a hand edit of the notes in the PR. The script passes ruff and ty, and the workflow passes actionlint.