bump-version

Automating semantic versioning and git tag creation requires computing the new version and preparing the exact commit and tag changes. This skill uses bump-my-version to calculate and apply patch, minor, or major increments, then switches branches and pushes tags to origin.

The safest way to bump version numbers involves checking for a clean working tree before starting, fetching the latest master from origin, and pushing annotated tags post-bump. This skill enforces these safety guardrails and returns you to the original branch at the end to maintain release consistency.

To prepare a release commit with bump-my-version, you switch to master, pull the latest changes, and apply the version increment. This skill streamlines that workflow by automatically computing the new version, applying the bump, and generating the expected commit and annotated tag.

Pushing git tags to origin with uncommitted changes is blocked by this skill to ensure deployment readiness. It requires a completely clean working tree before running branch switching, version bumping, and tag pushing operations to prevent corrupting the release state.

A release workflow requires switching to master before applying a version bump to ensure the tag reflects the latest origin state. This skill fetches and pulls master updates prior to using bump-my-version, satisfying release consistency and avoiding divergent branch tagging.

You need git and uv installed to automate DicePP release version bumps, alongside the bump-my-version package. These dependencies enable the skill to execute branch management, compute semantic versioning changes, and push annotated tags to the remote repository successfully.