Repository navigation
Add a release workflow and release 0.4.1 to PyPI - #20
Merged
Merged
Conversation
Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
… steps Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
Author
|
@chrisjkuch this should be good to go for running the release workflow immediately after merging |
Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
chrisjkuch
approved these changes
Nov 20, 2026
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.
Adds a Release workflow that publishes
pdc-apito PyPI and creates the GitHub release, points the README at PyPI, and bumps the version to 0.4.1 for the first PyPI release.Release workflow
Run it from the Actions tab with a tag such as
v0.5.0. It:main, the tag matches the version inpyproject.toml, the tag doesn't exist yet, andCHANGELOG.mdhas a dated heading for the version.hynek/build-and-inspect-python-package, with a build provenance attestation.test-pypienvironment.pypienvironment, which requires a reviewer and only allowsmain.Dry run is checked by default. A dry run stops after Test PyPI and prints what the release would contain. It needs no approval.
Both PyPI uploads use trusted publishing.
Docs
CONTRIBUTING.mdgets a Releasing section.AGENTS.mdsays releases go through the workflow and new changelog entries go under## Unreleased.README.mdinstalls from PyPI, and its CONTRIBUTING and LICENSE links are absolute so they work on the PyPI project page.CHANGELOG.mdhas a 0.4.1 entry announcing the PyPI package.Setup
test-pypienvironmentpypienvironment, with required reviewers and deployments only frommainAfter merging
Release 0.4.1 by following steps 2 to 5 of the new Releasing section in
CONTRIBUTING.md: a dry run onmainwith the tagv0.4.1, then the real run. If the release slips past 2026-11-20, update the date in the changelog first.Testing
Unreleasedheading.uv build,twine check --strict, andcheck-wheel-contentspass on the built package.mainbefore it can be dispatched.Assisted by Claude Code