Marketplaces can set metadata.pluginRoot so plugin entries resolve by bare name inside one folder.
What's wrong with this entry?
A 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.
- Applies only to bare source names; relative paths behave as before.
- pluginRoot must itself be a relative path contained by the marketplace root.
- No gate: this is plain marketplace loading.
Bare source names resolve under metadata.pluginRoot
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.246
Hook and command paths can start with $CLAUDE_PLUGIN_ROOT
Both mention root
-
v2.1.222
Commands, skills and plugin manifests accept a free-form metadata object
Both mention metadata
-
v2.1.222
Bad
metadatain frontmatter and manifests now warnsBoth mention metadata