Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Plugins reference missing `claude plugin tag` release-tag command [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52195•Fetched 2026-04-23 07:34:02
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/plugins-reference

Section/Topic

CLI commands reference and Distribution and versioning reference for plugin development

Current Documentation

The docs currently describe plugin management and versioning, but not the new release-tagging command.

From the CLI reference:

claude plugin | Manage Claude Code plugins. Alias: claude plugins. See plugin reference for subcommands

From the plugin reference:

Claude Code provides CLI commands for non-interactive plugin management, useful for scripting and automation.

plugin install

plugin uninstall

plugin enable

plugin disable

plugin update

From the versioning guidance:

  • Update the version in plugin.json before distributing changes

There is no documentation for claude plugin tag, creating release git tags for plugins, or the command's version-validation behavior.

What's Wrong or Missing?

Changelog v2.1.118 added claude plugin tag to create release git tags for plugins with version validation, but the Claude Code docs do not explain that this command exists.

That leaves the plugin release workflow incomplete: plugin authors can see install/update/versioning guidance, but not the CLI command for creating a release tag, what version source it validates, what tag it creates, or what errors users should expect when the plugin version is invalid.

Suggested Improvement

Add a ### plugin tag subsection to https://code.claude.com/docs/en/plugins-reference that documents:

  • command purpose and release workflow context
  • command syntax, arguments, and options
  • what version is validated (plugin.json, marketplace metadata, or both)
  • expected git tag naming/output behavior
  • failure cases when version validation does not pass
  • at least one example for tagging a normal release and one for a prerelease if supported

Also add a short cross-reference from https://code.claude.com/docs/en/plugins in the plugin-sharing/versioning guidance so plugin authors can discover the documented release flow.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/plugins-referencePlugin CLI subcommands and semantic-version guidance
https://code.claude.com/docs/en/cli-referenceTop-level claude plugin command entry should point readers to the new subcommand
https://code.claude.com/docs/en/pluginsPlugin sharing/versioning workflow for developers
https://code.claude.com/docs/en/plugin-marketplacesRelease-channel and version-resolution guidance may need a cross-reference to release tagging

Total scope: 4 pages affected

Source: Changelog v2.1.118

Exact changelog entry:

Added claude plugin tag to create release git tags for plugins with version validation

extent analysis

TL;DR

Add documentation for the claude plugin tag command to the plugins-reference page, including its purpose, syntax, and version validation behavior.

Guidance

  • Update the https://code.claude.com/docs/en/plugins-reference page with a new subsection ### plugin tag that documents the command's purpose, syntax, and behavior.
  • Include information on what version is validated (e.g., plugin.json, marketplace metadata, or both) and the expected git tag naming/output behavior.
  • Add examples for tagging a normal release and a prerelease (if supported) to help plugin authors understand the command's usage.
  • Create a cross-reference from https://code.claude.com/docs/en/plugins to point plugin authors to the documented release flow.

Example

### plugin tag
Create a release git tag for a plugin with version validation.

**Syntax:** `claude plugin tag <version>`
**Options:**
* `--validate`: Validate the plugin version against the `plugin.json` file.
* `--prerelease`: Create a prerelease tag.

**Example:**
```bash
claude plugin tag 1.2.3

This will create a release git tag v1.2.3 for the plugin.

Notes

The documentation update should cover the command's behavior, including failure cases when version validation does not pass.

Recommendation

Apply workaround: Add the missing documentation to the plugins-reference page to provide a clear understanding of the claude plugin tag command and its usage.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#model save/load#optimization#mixed precision#training loop#device allocation

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING