{"version":"2.1.239","anchor":"marketplaces-can-list-plugins-by-bare-name-under-metadata-pl","canonical_anchor":"marketplaces-can-list-plugins-by-bare-name-under-metadata-pl","heading":"Marketplaces can list plugins by bare name under metadata.pluginRoot","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/marketplaces-can-list-plugins-by-bare-name-under-metadata-pl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Marketplaces can list plugins by bare name under `metadata.pluginRoot`\n\nMarketplaces can set metadata.pluginRoot so plugin entries resolve by bare name inside one folder.\n\n**What**\n\nA plugin marketplace file can now declare `metadata.pluginRoot` once at the top, and entries whose `source` is a bare name (not a `.\/relative\/path`) are resolved inside that folder. If pluginRoot is absent, or points outside the marketplace directory, the entry loads as a stub carrying an explanatory error rather than failing quietly.\n\n**Details**\n\n- Applies only to bare source names; relative paths behave as before.\n- pluginRoot must itself be a relative path contained by the marketplace root.\n- No gate: this is plain marketplace loading.\n\n**Evidence**\n\n`Bare source names resolve under metadata.pluginRoot`\n\n- Area: Plugins\n- Names: `metadata.pluginRoot`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}