CI: add a simple tag-to-release config #349
Merged
Conversation
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
This adds a tag-to-release Actions config based around uv. This is triggered by pushing a tag with a new version; it will automatically kick off this job, which will publish the new version to PyPI on completion. We can push that tag from a PR or directly to master. At the moment, this doesn't do anything to automatically create a GitHub release from the tag; we can do that manually for now, but if we're interested I can add something to automatically generate the release too. We don't need to provide a token to uv to publish; instead, we just need to configure the repo for PyPI access using this: https://docs.pypi.org/trusted-publishers/adding-a-publisher/
gretchenleighmiller
approved these changes
Apr 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds a tag-to-release Actions config based around
uv.This is triggered by pushing a tag with a new version; it will automatically kick off this job, which will publish the new version to PyPI on completion. We can push that tag from a PR or directly to master.
At the moment, this doesn't do anything to automatically create a GitHub release from the tag; we can do that manually for now. We don't currently have in-repo release notes for us to build an automated release from so this would be a largely manual process anyway.
We don't need to provide a token to
uvto publish; instead, we just need to configure the repo for PyPI access using this: https://docs.pypi.org/trusted-publishers/adding-a-publisher/cc @vbanos