What
Plugin installs now carry a flag saying whether you asked for the plugin directly or it came in as a dependency, along with consent state passed down from the caller. Updates blocked by a version pin now report the reason as pinner_blocked rather than failing silently, and a plugin that cannot be found raises a specific error instead of quietly becoming nothing.
Details
- Callers pass
explicitInstallandconsented; installs done to satisfy a dependency are marked as not explicit. - Two new in-memory caches were added to plugin state for marketplace helper lookups and directory-scoped marketplaces.
Evidence
skipReason: "pinner_blocked",
Strings lifted out of the shipped bundle, so the claim above can be checked against them.