Release

This command handles version management for the mx-workflow plugin, keeping version numbers, changelogs, and git tags in sync.

/mx:version

Bump version in plugin.json + marketplace.json, update CHANGELOG, commit, and tag

/mx:version <patch|minor|major|x.y.z>

Centralized version management that bumps the version across all manifest files, updates the changelog, commits the changes, and creates a git tag — all in one step. It ensures that plugin.json, .claude-plugin/marketplace.json, and CHANGELOG.md stay in sync.

Argument	Effect	Example
patch	Increment the patch version	1.0.1 becomes 1.0.2
minor	Increment the minor version	1.0.1 becomes 1.1.0
major	Increment the major version	1.0.1 becomes 2.0.0
x.y.z	Set an explicit version number	2.1.0 sets the version to 2.1.0

What it updates

1. plugin.json — the version field
2. .claude-plugin/marketplace.json — the plugins[0].version field
3. CHANGELOG.md — moves content from the [Unreleased] section into a new version section with the current date
4. Git — creates a commit and a v{version} tag

Examples

Bump the patch version after a bug fix:

/mx:version patch

Bump the minor version after adding a new command:

/mx:version minor

Set an explicit version for a major release:

/mx:version 2.0.0

When to bump

Change type	Version bump
Bug fixes, typo corrections, doc-only changes	patch
New commands, new agents, new features, non-breaking improvements	minor
Breaking changes to existing command behavior or plugin structure	major

When to use it:

• After completing a batch of work that is ready for release
• When you need to create a versioned release with a changelog entry
• Before creating a GitHub Release with gh release create