Repository navigation
Automate PyPI releases from version tags - #20
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The release flow commits before checking for an existing tag, so a duplicate tag leaves master ahead of origin/master and blocks a corrected retry at the sync check.
1 open issue
What changed in this PR
Automates the Python package’s release process, from local validation and version tagging to publishing on PyPI and creating a GitHub release.
Changes:
- Adds
make release VERSION=x.y.zto check repository state, run tests, bumpVERSION, and create a release commit and tag. - Adds a version-tag-triggered workflow using PyPI trusted publishing through the
releaseenvironment. - Documents the release commands.
| File | Description |
|---|---|
| README.md | Documents how to prepare and push a release. |
| Makefile | Adds local release checks, version updates, commits, and tagging. |
| .github/workflows/release.yml | Validates tags, tests and builds the package, publishes to PyPI, and creates a GitHub release. |
Review effort: Balanced
4c177dd to
bf6c9dd
Compare
There was a problem hiding this comment.
🟡 Changes recommended
Release automation accepts leading-zero versions that can collide with existing PyPI releases and lacks skip-existing, leaving reruns blocked by duplicate uploads after a GitHub release failure.
2 open issues
1 resolved since last review
Review effort: Balanced
Releases were published by hand, so a step like bumping VERSION or creating the GitHub release could be missed. Pushing a tag made by `make release` now publishes to PyPI through trusted publishing.
bf6c9dd to
1037ed3
Compare
There was a problem hiding this comment.
🔵 Needs a closer look
The release environment’s tag-only deployment rules and PyPI trusted publisher configuration are not visible in this PR and must be verified before publishing is enabled.
No open issues 🎉
2 resolved since last review
Review effort: Balanced

Releases were published by hand, so a step like bumping
VERSIONor creating the GitHub release could be missed. Runningmake release VERSION=x.y.znow checks the branch and tests before tagging, and pushing the tag publishes to PyPI through trusted publishing from areleaseenvironment that only version tags can deploy to. Before the first release, add a PyPI trusted publisher forrelease.ymlwith environmentrelease.