plugin-version-bump

To automate version bumps for Claude Code plugins, this skill updates version strings in .claude-plugin/plugin.json and marketplace registry entries simultaneously. It enforces semver-like rules and prevents partial updates by applying guardrails that keep all related metadata files synchronized.

Keeping plugin.json and marketplace versions in sync is handled by applying a synchronized version bump across local and registry records. The skill respects existing file structures and ensures all related metadata shares a consistent version string after plugin code changes.

You need to update the version in a Claude Code plugin registry whenever a plugin's code or metadata changes and a synchronized bump across local and registry records is required. This maintains consistency between the root marketplace registry and local plugin configurations.

The version bump workflow does follow semver-like rules for marketplace entries. It updates multiple files to consistent version strings while respecting the existing plugin.json and marketplace structures to ensure semantic versioning compliance across the repository.

You can prevent partial version updates because this skill provides guardrails to ensure all related files share a consistent version. It updates plugin.json and marketplace entries together, avoiding desynchronized records after plugin modifications.

To update plugin metadata versions after changes, invoke the bump action once your plugin code modifications are complete. The skill synchronizes plugin.json and marketplace versions across the repository, applying semver-like rules to maintain consistent version strings.