release

To automate a PyPI release through a PR flow, this Skill validates that main is clean, creates a release branch, bumps versions, updates changelogs, and opens a PR. After CI passes and merges, it pushes an annotated git tag to trigger PyPI publishing.

Automating version bumps and changelog updates is handled by creating a dedicated release branch where version numbers in files like __init__.py and both English and Japanese changelogs are updated automatically before a pull request is created.

Pushing an annotated git tag triggers CI and PyPI publishing by matching a tag pattern like v*, which automatically activates the release.yml workflow to build and upload the package to PyPI after the release PR merges.

You cannot use this release orchestration if your main branch is not clean. The workflow explicitly validates that the main branch is in a clean state before allowing the creation of a release branch to ensure release stability.

Yes, this workflow supports maintaining changelogs in both English and Japanese. The automated release process concurrently updates both language changelog files alongside the version bump in the codebase before creating the pull request.

A PR-based workflow for software releases is needed to enforce CI verification before merging. It ensures that version bumps, changelog updates, and code changes pass all checks before an annotated tag is pushed to trigger the final PyPI deployment.