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 pull request updates the release workflow and documentation to support publishing Python packages to PyPI, improve release notes, and clarify installation instructions.
Instructions for setting up the PyPi OIDC trust are annotated in #204
TLDR; Adds python package artifacts to GH release and publishes to PyPi, enabling:
The most important changes are grouped below:
Release Workflow Enhancements
pyproject.toml
, building withuv
, and publishing withuv publish
. [1] [2].whl
) and source distribution (.tar.gz
) files alongside template zip files as release assets.pypi
and addedid-token: write
permission to support secure publishing to PyPI.actions/checkout
to version 5 and added a step to installuv
usingastral-sh/setup-uv@v6
.Documentation and Versioning
README.md
to recommend PyPI installation and clarified usage for both PyPI and Git-based installs.3.11
in the.python-version
file for consistency in development and CI environments.