Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.323entry #67

Claude Code v2.1.323 ·

Plugin updates can target a specific older version or tag

Plugin updates can now aim at a specific older version or tag instead of always the latest one

Use it now New Features
JSON All of v2.1.323
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
New FeaturesKind: in v2.1.323,
What probably matters to youSection of the release

Unclear It is not clear whether any command lets you ask for a specific plugin version yet.

What

Updating a plugin can now aim at a specific version or tag, and compares it with the version you have installed. Before, an update always went to the latest version in the catalog. New messages cover the cases where the installed plugin is already past the requested version, or was not updated to that version. Update messages can also carry an extra note.

Two smaller changes come with it:

  • Installing a plugin's dependencies is now skipped in some cases.
  • The separate handling for disabled npm marketplaces has been removed.
Why

This looks like groundwork for pinning a plugin to a version or rolling back to an earlier one.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether any command lets you ask for a specific plugin version yet.

See this entry in the whole of v2.1.323 →

Feedback