release

Automate a Python package release by running a workflow that verifies a clean main branch, runs tests and linting, calculates versions, updates the changelog, builds, and creates Git tags. This handles the full release process from pre-flight checks to tagging automatically.

Pre-flight checks for a Python release ensure you are on a clean main branch with an updated working directory. The workflow validates branch state, runs tests and linting, and confirms the changelog is refreshed before calculating versions and pushing Git tags.

Version calculation for Python packages using uv and ruff automatically determines the next release number or accepts a version override. The workflow computes the version after pre-flight checks and applies it before updating the changelog and creating Git tags.

Yes, you can override the automatically calculated version during a Python package release. The workflow accepts a manual version override after completing pre-flight checks and before it proceeds to update the changelog and create Git tags.

Yes, the Python release workflow requires running on a clean main branch with a verified working directory. This requirement ensures pre-release checks pass correctly before proceeding to version calculation, changelog updates, and Git tag creation.

Update changelog entries before a Python release by optionally invoking a changelog agent that refreshes Unreleased entries. The workflow then applies the updated changelog alongside version calculation and Git tag creation during the release process.