bump-version

Automated version bumping across multiple components is handled by incrementing patch, minor, or major versions based on your input, then synchronizing those updates across JSON configurations, READMEs, and changelogs to ensure consistency.

Independent version tracks for a marketplace, coding system, and productivity suite can be managed by applying separate version increments to each component, updating their respective configuration files and changelogs individually.

Updating changelogs and JSON configurations during a version release involves synchronizing the newly incremented version numbers across critical files like marketplace.json, plugin.json, README.md, and CLAUDE.md automatically.

You need jq installed as a dependency to automate multi-track release management, because it enables the Skill to parse and modify JSON configuration files like marketplace.json and plugin.json during the version increment process.

The best way to keep version numbers consistent across related projects is to automate the synchronization process, updating version declarations in documentation and configuration files simultaneously to eliminate manual errors.

The type of version bump for a release requires user input to determine which specific components have changed and whether the increment should be a patch, minor, or major version update.