{"version":"2.1.251","anchor":"stricter-checks-before-a-cached-plugin-install-is-reused","canonical_anchor":"stricter-checks-before-a-cached-plugin-install-is-reused","heading":"Stricter checks before a cached plugin install is reused","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/stricter-checks-before-a-cached-plugin-install-is-reused","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Stricter checks before a cached plugin install is reused\n\nCached plugin installs are re-verified against trusted roots before being reused.\n\n**What**\n\nResolving a plugin from a marketplace now re-derives the trusted roots and rejects an install path it considers suspect before treating the cached copy as current. For plugins served in place from a command-provided source, it confirms the source really is a directory of links rather than accepting a path that merely looks like one.\n\n**Details**\n\n- when the cached copy cannot be safely reused, the error says the plugin is served in place from a path that could not be resolved or no longer matches its cached links\n- always on; there is no setting to skip the extra checks\n\n**Evidence**\n\n`it is served in place from`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}