{"version":"2.1.287","anchor":"plugin-dependency-pinning-and-missing-dependency-warning-for","canonical_anchor":"plugin-dependency-pinning-and-missing-dependency-warning-for","heading":"Plugin dependencies from one marketplace get version checks and missing warnings","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/plugin-dependency-pinning-and-missing-dependency-warning-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Plugin dependencies from one marketplace get version checks and missing warnings\n\nDependencies from one particular marketplace now check version ranges and warn when they could not be installed, with the reason\n\n**Unclear.** Which marketplace this applies to, and when `--filter=tree:0` is still used, is not known.\n\n**What**\n\nA plugin can depend on other plugins. For dependencies that come from one particular marketplace (a catalogue plugins are installed from), installing and loading changed:\n\n- Version ranges: a dependency pinned to a range of versions is checked against the commit the marketplace lists.\n\n- Missing dependencies: you now get a warning that the dependency was not installed, saying whether the marketplace is turned off, blocked by your organization, or does not list it.\n\n- Loading: Claude Code will not download missing files again when the commit the marketplace lists is different.\n\n- Cloning: when fetching a plugin from a subfolder of a git repository, Claude Code now uses `--filter=tree:0` only in some cases. Before, it always did.\n\n**Why**\n\nPlugins from this marketplace install and load differently, and a dependency that silently failed to install now says why.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}