bump-version

To sync version numbers across plugin config files, provide a new version string to update and verify the version field in plugin.json and marketplace.json files. This ensures all configurations reflect the identical version without requiring manual edits.

Automating version bumps for marketplace.json and plugin.json files involves reading the target configurations, replacing the old version string with the new value, and verifying consistency. This non-destructive process updates three specific files without committing changes.

Version drift in plugin release workflows happens when configuration files are updated manually at different times. Prevent drift by batch updating the version string across plugin.json and marketplace.json files simultaneously, ensuring all files match before committing.

No, the version update process does not commit changes directly to the repository. It operates as a non-destructive workflow that reads three target files, applies the new version, verifies they match, and leaves the changes uncommitted for audit purposes.

Yes, you can verify version consistency across plugin directories before finalizing a release. The process checks that all three target config files, including the arc-probe plugin.json, report any mismatches, ensuring a unified version without committing.

When bumping a version in a plugin directory, you need to update the version field in plugin/.claude-plugin/plugin.json, public-repo/.claude-plugin/marketplace.json, and public-repo/plugins/arc-proe/.claude-plugin/plugin.json to maintain configuration consistency.