make-release

You can automate PyPI releases via GitHub Actions by triggering a script with a SemVer version that runs quality checks, bumps versions in project files, updates the changelog, tags the commit, and publishes the package.

A Python release workflow automation script includes validating a clean working tree on the main branch, bumping versions in pyproject.toml and __init__.py, promoting changelog entries, creating a git tag, and publishing to PyPI.

Yes, publishing to PyPI requires a clean working tree on the main branch and an updated changelog. The workflow enforces these prerequisites and runs quality checks before bumping versions and tagging the release commit.

Version bumping during a release updates the version strings in both pyproject.toml and __init__.py based on the provided SemVer input, ensuring project metadata and runtime versions stay synchronized before tagging and publishing.

Yes, you can generate release notes and git tags automatically for Python projects. The workflow creates a release notes entry from the changelog and applies a git tag to the commit before pushing and publishing to PyPI.

If quality checks fail during release automation, the workflow halts before performing any version bumps, changelog updates, or git tagging operations, ensuring that only validated code is published to PyPI.