{"version":"2.1.323","anchor":"plugin-manifest-engines-validation","canonical_anchor":"plugin-manifest-engines-validation","heading":"Plugin manifests now check the engines version range","tier":"use","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-manifest-engines-validation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Plugin manifests now check the engines version range\n\nClaude Code now warns when a plugin's engines field is not an object or its claude-code entry is not a version range\n\n**What**\n\nA plugin's manifest file, `plugin.json`, can now carry an `engines` field that says which versions of Claude Code the plugin supports. Validation reports a problem in two cases:\n\n- `engines` is not an object\n\n- `engines.claude-code` is not a version range, such as `\">=2.1.0\"`\n\nWhen a plugin loads, Claude Code ignores either kind of bad value. Marketplace validation applies the same check to the `engines` field of each plugin listed in a marketplace. A marketplace is a catalogue that offers plugins for install.\n\n**Why**\n\nPlugin authors find out early when their version constraint is written wrong, instead of having it silently ignored.\n\n- Area: Plugins\n- Names: `engines`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}