bumping-version

To automate semantic version bumps, this Skill analyzes commits since the last bump, suggests a semver level with rationale, updates the plugin version and changelog, then commits and pushes the changes automatically.

Automatic semantic versioning analyzes commit history since the last version bump to identify the affected scope, then suggests the appropriate semver level with rationale and prompts the user for confirmation before applying any file changes.

Yes, you can use this to prepare a release without manual edits; it automatically updates the plugin.json version and prepends a new generated changelog entry based on the analyzed commit history before committing.

The version bumping workflow enforces these steps: detect the last bump commit, generate a changelog entry, increment the version, update the plugin files, commit the changes, and push to the remote repository.

No, you do not need to manually specify the increment level; the Skill suggests a patch, minor, or major semver bump by analyzing the change scope from your commits and prompts you for confirmation before proceeding.

The automated release process requires pushing changes to git immediately after the version bump to enforce the workflow steps, ensuring the updated plugin.json version and prepended changelog entry are committed and synchronized to the remote repository.