{"version":"2.1.287","anchor":"pinned-directory-plugins-now-give-an-explanatory-error-when","canonical_anchor":"pinned-directory-plugins-now-give-an-explanatory-error-when","heading":"Pinned plugins that miss a required version now explain why","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/pinned-directory-plugins-now-give-an-explanatory-error-when","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Pinned plugins that miss a required version now explain why\n\nWhen a pinned plugin's version does not fit what other plugins require, the error now says which version, which range and who needs it\n\n**What**\n\nA plugin can be pinned, meaning held to one specific commit. When a pinned plugin's version does not fall within the range that other plugins require, Claude Code reports a failure. That failure used to have an empty message. It now says:\n\n- that the plugin is pinned to the commit its source lists\n\n- its version, or \"no version\" if it has none\n\n- the version range that is required\n\n- which plugins require it\n\n**Why**\n\nAn error that used to be blank now tells you what to fix: update the pin or change what the other plugins require.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}