{"version":"2.1.273","anchor":"artifact-publish-overhauled-unservable-file-type-error-mess","canonical_anchor":"artifact-publish-overhauled-unservable-file-type-error-mess","heading":"Artifact publish: overhauled unservable-file-type error messages with new content-type taxonomy","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/artifact-publish-overhauled-unservable-file-type-error-mess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Artifact publish: overhauled unservable-file-type error messages with new content-type taxonomy\n\nArtifact publish errors for unservable file types now explain what to do, grouped by category\n\n**What**\n\nWhen publishing an artifact fails because a file's content type isn't one Claude Code can serve, the error message is now far more detailed. It groups servable content types into categories such as pages, styles, scripts, data, images, fonts, media, and documents, lists which file extensions belong to each, and gives targeted advice, for example pointing out when a rejected type has a close servable alternative, or when the file extension is a recognized but unservable type.\n\nClaude Code also now records `refused_ext` and `refused_type` details in its `artifact_publish` \/ `file_not_servable` telemetry event.\n\n**Why**\n\nInstead of a bare rejection, users publishing an artifact now get concrete guidance on why a file's type isn't supported and what servable alternative to use instead.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}