{"version":"2.1.234","anchor":"publishing-an-artifact-can-now-report-that-the-outcome-is-un","canonical_anchor":"publishing-an-artifact-can-now-report-that-the-outcome-is-un","heading":"Publishing an artifact can now report that the outcome is unknown","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/publishing-an-artifact-can-now-report-that-the-outcome-is-un","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Publishing an artifact can now report that the outcome is unknown\n\nAn unconfirmable artifact publish now says the outcome is unknown and to check before republishing.\n\n**What**\n\nWhen a publish attempt cannot be confirmed, Claude Code says so instead of reporting a flat failure, and tells you to check the artifact list before publishing again. Relay HTTP errors, thrown requests, replies about the wrong artifact and malformed replies all land here.\n\n**Details**\n\n- The automatic comment-edit pipeline maps this to a distinct failure kind with its own reply text and its own thread notice, separate from the existing failure wordings.\n- No flag gates the wording; it is reached whenever the publish reply does not come from the expected frame or the request throws.\n\n**Evidence**\n\n`it may have published; check the artifact list before publishing again`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}