{"version":"2.1.271","anchor":"artifact-publish-unknown-capability-error-now-explains-con","canonical_anchor":"artifact-publish-unknown-capability-error-now-explains-con","heading":"Artifact publish 'unknown capability' error now explains contract-pinning mismatches","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifact-publish-unknown-capability-error-now-explains-con","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Artifact publish 'unknown capability' error now explains contract-pinning mismatches\n\nArtifact publish errors now explain when an unknown capability is just from an older pinned contract\n\n**What**\n\nWhen publishing an artifact fails because it references a capability Claude Code doesn't recognize, the error message now checks whether that capability actually exists in the current, up-to-date list of known capabilities. If it does, the error explains that the publish is pinned to an older contract version, either because the caller explicitly requested that older contract or because the artifact's own stored data specifies it.\n\n**Why**\n\nThis turns a confusing \"unknown capability\" error into an explanation that the mismatch is due to version pinning, making it clear the fix is a version issue rather than a genuinely unsupported feature.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}