{"version":"2.1.284","anchor":"artifact-publish-type-locked-422-hint-now-depends-on-the-ty","canonical_anchor":"artifact-publish-type-locked-422-hint-now-depends-on-the-ty","heading":"Artifact publish errors for type-locked instances show a hint that depends on a setting","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/artifact-publish-type-locked-422-hint-now-depends-on-the-ty","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Artifact publish errors for type-locked instances show a hint that depends on a setting\n\nWhen publishing an artifact to a type-locked instance fails, Claude Code now picks between two hint texts, or none, based on a setting\n\n**Unclear.** What the two hint texts actually say is not known.\n\n**What**\n\nAn artifact is a piece of output Claude Code can publish. When publishing one fails because the destination instance only accepts certain types, Claude Code adds a hint to the error. It now chooses the hint like this:\n\n- `frozenArtifactTypes.typesOn` true: one hint text\n\n- `frozenArtifactTypes.typesOn` false: a different hint text\n\n- `frozenArtifactTypes.typesOn` not set: no hint\n\nBefore, a hint appeared only when that value was on. Artifact errors now also carry a cleaned-up reason from the server.\n\n**Why**\n\nThis is a small change to publish error messages. A failed publish can now explain itself in either state of the setting, not only when it is on.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}