bump-plugin-version

To automate version bumps for Claude Code plugins, you can use a skill that reads plugin.json and marketplace.json, updates the version fields, and then commits and tags the release automatically to ensure traceability. This works for both single plugins and bulk updates.

Keeping marketplace.json and plugin.json versions in sync requires updating both files consistently during a release. An automated versioning skill reads these manifest files, computes the appropriate version bump, and applies the updates across all related references simultaneously to prevent data mismatch.

Yes, you can bump all plugin versions in a marketplace at the same time by running the versioning automation without specifying a plugin name. It calculates the appropriate version bumps across the entire plugin set and updates the marketplace data and per-plugin manifests in bulk.

To commit and tag plugin releases automatically, the version bumping process triggers git commit and tag steps immediately after updating the version fields in the manifest files. This records the release and enables traceability without requiring manual git commands.

No, you do not need to manually edit plugin.json to change a plugin version. The automation skill reads the existing manifest, computes the new version based on your release scope, and writes the updated version fields directly into the file before committing the changes.