What
A new slash command and CLI subcommand to create versioned git tags for plugin releases, with validation against plugin.json and marketplace entries.
Usage
/plugin tag [path] [--push] [--dry-run] [-f|--force]
claude plugin tag [path] [--push] [--dry-run] [-f|--force] [-m <msg>] [--remote <name>]
Details
- Validates plugin.json and any enclosing marketplace manifest agree on name and version
- Checks for uncommitted changes, existing tags, valid semver, and valid git ref names
- Creates annotated git tags in the format
{name}--v{version} --push pushes the tag to the remote after creation--dry-run previews what would be tagged without creating it--force skips dirty-working-tree and tag-already-exists checks- CLI variant adds
--message <msg> for custom tag annotation and --remote <name> for push target - Detailed error messages for version mismatches, missing manifests, and invalid configs
Evidence
Slash command help text (search for "Create a {name}--v{version} git tag") and CLI subcommand .command("tag [path]") at line ~652882.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded claude plugin tag to create release git tags for plugins with version validation
See this entry in the whole of v2.1.118 →