Skip to content

ci(release): tag and create the GitHub release when the PR merges - #783

Merged
masquare merged 1 commit into
ci/release-open-prfrom
ci/release-tag
Nov 13, 2026
Merged

masquare merged 1 commit into
ci/release-open-prfrom
ci/release-tag

Conversation

@masquare

@masquare masquare commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Stack: automated per-package releases. Review the PRs in this order. Each PR shows only its own layer.

  1. ci(release): generate release notes per package #781 Release notes
  2. ci(release): open a release PR and tag the release when it merges #782 Open a release PR
  3. ci(release): tag and create the GitHub release when the PR merges #783 Tag and create the GitHub release
  4. ci(release): publish the built files to TestPyPI and PyPI #784 Publish to TestPyPI and PyPI
  5. ci(release): open the PR for the next development version #785 Open the next development version PR

main keeps working after each merge. Nothing changes how packages are published until PR 4 deletes publish.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

  • Trigger: a push to main whose commit message starts with chore(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.
  • Permissions: contents: write and pull-requests: read, for this job only.

Not in this PR

Uploading to TestPyPI and PyPI. publish.yml still 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.

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
masquare marked this pull request as ready for review November 13, 2026 15:32
@masquare
masquare requested a review from karhu November 13, 2026 15:33
@masquare
masquare merged commit 46c4cdd into ci/release-open-pr Nov 13, 2026
7 of 11 checks passed
@masquare
masquare deleted the ci/release-tag branch November 13, 2026 15:39
@masquare

Copy link
Copy Markdown
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant