Answer: If you publish through your own marketplace and your plugin.json sets version, increment it and push so users who run `claude plugin update` or have auto-update on receive the new version. Never change a published plugin's name; if a rename is unavoidable, use the marketplace file's `renames` map so existing installs migrate, and to remove a plugin from the marketplace see the hosting page. Status: Confirmed Entry: tool/claude-code/integrations/plugin-updates-renames-removals Revision: 3 Digest: sha256:f06dd5f331659d20 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:05:23Z Last changed: 2026-11-19T12:19:28Z (Rename migration mechanism: — → `renames` map) Last verified: 2026-11-20T12:24:06Z Next check: 2026-11-21T12:24:06Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Update method | increment it and push | [1] | 2026-11-20 User update command | claude plugin update | [1] | 2026-11-20 Rename rule | Never change a published plugin's `name` | [1] | 2026-11-20 Rename migration mechanism | `renames` map | [1] | 2026-11-20 Tag command | claude plugin tag | [1] | 2026-11-20 Tag format | {name}--v{version} | [1] | 2026-11-20 Sources: [1] Anthropic. "Publish and distribute a plugin". https://code.claude.com/docs/en/plugins/publish.md Role: primary. Accessed: 2026-11-20T12:24:06Z Quote: "increment it and push" (Supports: Update method) Quote: "Users who run `claude plugin update` or have auto-update on then receive the new version" (Supports: User update command) Quote: "Never change a published plugin's `name`." (Supports: Rename rule) Quote: "use the marketplace file's `renames` map so that existing installs migrate" (Supports: Rename migration mechanism) Quote: "run `claude plugin tag` in your shell from the plugin directory" (Supports: Tag command) Quote: "It creates a `{name}--v{version}` tag." (Supports: Tag format) Published: 2026-11-20T02:53:11Z Snapshot SHA-256: 83da0dae13e713af29ed56401dd5dd955ffe72b15232d7552d6e9efd613562f0 (captured 2026-11-18T12:19:17Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T12:19:18Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:24:06Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:24:06Z Last attempt: 2026-11-20T12:24:06Z Notes and limitations: Extracted automatically from a single official source (section "Ship updates, renames, and removals"). Related: https://latestn.com/tool/claude-code/integrations/project-github-access How do I set up GitHub access for a Claude Code project? https://latestn.com/tool/claude-code/integrations/publish-plugin-own-marketplace How do I publish and distribute a Claude Code plugin through my own marketplace? https://latestn.com/tool/claude-code/integrations/read-review-result-from-script How do I read Claude Code review results from a script using the check run output? https://latestn.com/tool/claude-code/integrations/package-name-changes What package names changed when Claude Code SDK was renamed to Claude Agent SDK? https://latestn.com/tool/claude-code/integrations/pipe-claude-into-scripts How do I pipe Claude Code into scripts for automation? https://latestn.com/tool/claude-code/integrations/plugin-source-types What plugin source types can I use in a Claude Code marketplace.json? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T12:19:28Z | changed | Rename migration mechanism: — → `renames` map | [1] 2026-11-19T12:19:28Z | changed | Label field: displayName → — | [1] 2026-11-19T12:19:28Z | changed | Rename migration field: renames → — | [1] 2026-11-19T12:19:28Z | changed | Rename rule: Never change a published plugin's `name`. → Never change a published plugin's `name` | [1] 2026-11-14T12:19:53Z | changed | Label field: — → displayName | [1] 2026-11-14T12:19:53Z | changed | Rename rule: Never change a published plugin's `name` → Never change a published plugin's `name`. | [1] 2026-11-13T03:05:23Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/integrations/plugin-updates-renames-removals/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/integrations/plugin-updates-renames-removals POST: https://latestn.com/dispute/tool/claude-code/integrations/plugin-updates-renames-removals with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/integrations/plugin-updates-renames-removals?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I ship updates, renames, or removals of a Claude Code plugin to users? Revision 3, last verified 2026-11-20T12:24:06Z. https://latestn.com/tool/claude-code/integrations/plugin-updates-renames-removals (accessed 2026-11-21T09:55:04Z). @misc{LatestN_tool_claude_code_integrations_plugin_updates_renames_removals_r3, title = {How do I ship updates, renames, or removals of a Claude Code plugin to users?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/integrations/plugin-updates-renames-removals}}, note = {Revision 3; digest sha256:f06dd5f331659d20; last verified 2026-11-20T12:24:06Z; accessed 2026-11-21T09:55:04Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/integrations/plugin-updates-renames-removals