You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.239,
ImprovementsSection of the release
What
A bare plugin source in a marketplace file now fails with a message naming the source and telling you to either use a ./relative/path or set metadata.pluginRoot. Reserved plugin names are also checked against a single table now instead of one rule per name.
Details
Reserved names covered by the table: inline, builtin and skills-dir.
Full message: Bare source name "${b}" requires metadata.pluginRoot. Use "./relative/path", or set metadata.pluginRoot (e.g. "./plugins") to allow bare names.
Evidence
Bare source name "${b}" requires metadata.pluginRoot. Use "./relative/path", or set metadata.pluginRoot (e.g. "./plugins") to allow bare names.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed marketplace metadata.pluginRoot having no effect: bare plugin source names now resolve under it as the docs describe
