Publishing an artifact page that declares MCP capabilities but omits previously-stored capabilities, while also adding new ones, is now rejected with an explicit error instead of silently revoking the missing capabilities. To drop capabilities intentionally, republish with the full union or use an explicit 'latest' contract.
Workshop/artifact publish now refuses capability retrofits that would silently drop capabilities
Republishing a page that omits previously-stored MCP capabilities is now rejected instead of silently revoking them.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Bug FixesKind: in v2.1.257,
Bug FixesSection of the release