bump-version

To bump a plugin version automatically, the Skill increments the semantic version component in plugin.json and rewrites the file. It determines the target plugin from a provided name or session context, then applies the chosen major, minor, or patch increment.

Semantic versioning uses major, minor, and patch numbers. When bumping a version, the Skill increments the chosen component and automatically resets all lower-order components to zero to maintain proper versioning format.

You can update plugin metadata without specifying a name. The Skill infers the target plugin from the session context and prompts for confirmation before applying the version bump to the plugin.json file.

The best way to increment a minor release version is to use a bump-version command targeting the specific plugin. It reads the current version, increments the minor number, resets the patch number, and writes the update to plugin.json.

Yes, the version bumping process prompts for confirmation. If no explicit target plugin is provided, it infers the plugin from session context and requests confirmation before modifying the plugin.json file.

You need to bump a major version when introducing breaking changes, while patch increments are for fixes. The Skill applies the chosen increment and resets lower-order components in the plugin.json file accordingly.