AI News
All stories
Official

Claude Code plugins can declare a version range and skip out-of-range installs

Claude Code 2.1.323 lets plugins state a supported Claude Code version range in plugin.json, and plugins outside that range are not installed, updated or loaded.

Products · · 1 min read

Claude Code 2.1.323 adds an engines["claude-code"] field to plugin.json. A plugin that declares a Claude Code version range outside the one it states is not installed, updated or loaded. The changelog for the release, dated November 12, 2026, describes the field in one line: install and update pick the newest plugin version that fits the user's Claude Code version.

The practical effect falls on plugin authors and on the people installing their plugins. With the new field, the author states the range once in the manifest. Claude Code then applies it at three points: installation, updating and loading.

When several versions of a plugin exist, install and update choose the newest one whose range includes the user's Claude Code version. An author who ships a new plugin release for a newer Claude Code can therefore leave an older user on a previous plugin release that still fits, rather than leaving that user with nothing.

The same release contains related changes to plugin validation. The changelog says `claude plugin validate` now type-checks a plugin's TypeScript hooks module, and that each finding is a warning. With `--strict`, warnings become failures. The changelog also notes that `claude plugin install` and `/plugin` now show a warning instead of success when an install command writes to stderr. A plugin's `agent` setting is deprecated. It still applies, but it now produces a startup warning.

A plugin outside its declared range is skipped before it is loaded.

The changelog entry gives no range syntax, no example manifest, and no information on how authors will test a range or how many releases a range may span. The entry is also listed under Added, so the feature appears in this release with no note that it is experimental. The same list marks Code Mode as an opt-in experiment.

What changed

Plugins can now declare a supported Claude Code version range through an engines["claude-code"] field in plugin.json, and plugins outside that range are not installed, updated or loaded.

Type: New capability · Takes effect: Thursday, November 12, 2026 · Applies to: Claude Code 2.1.323, plugin.json

Why it matters

Plugin authors can avoid breaking users on incompatible Claude Code releases, but teams need to confirm their plugins declare a valid range.

What you can do

Ask internal plugin authors to declare the supported Claude Code range in plugin.json.

Original source

Where we saw it

1 source

Claude Code changelog

AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works