{"version":"2.1.296","anchor":"plugin-dependency-matching-now-takes-the-dependents-source","canonical_anchor":"plugin-dependency-matching-now-takes-the-dependents-source","heading":"Plugin dependency checks now consider where the depending plugin came from","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/plugin-dependency-matching-now-takes-the-dependents-source","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Plugin dependency checks now consider where the depending plugin came from\n\nWhen matching plugin dependencies, Claude Code now also uses the source of the plugin that declares the dependency\n\n**Unclear.** It is not known exactly which dependencies now match differently than before.\n\n**What**\n\nPlugins are add-ons that extend Claude Code, and a plugin can list other plugins it depends on. Three checks that match these dependencies now also take into account the source of the plugin that declares them, such as the marketplace (plugin catalogue) it was installed from. These checks include the one that works out which plugins depend on a given plugin.\n\n**Why**\n\nThis can change which plugins Claude Code treats as depended on, for example when you disable a plugin that another one needs. Dependencies written relative to a plugin's own source, or scoped to a marketplace, may now resolve differently.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}