{"version":"2.1.309","anchor":"artifact-publish-fails-closed-when-org-requires-per-artifact","canonical_anchor":"artifact-publish-fails-closed-when-org-requires-per-artifact","heading":"Artifact publishing gets its own refusal reason when each artifact needs approval","tier":"notice","area":"Artifacts","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/artifact-publish-fails-closed-when-org-requires-per-artifact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Artifact publishing gets its own refusal reason when each artifact needs approval\n\nPublishing an artifact is now refused with a specific reason when its permission check cannot finish and your organization requires approval for each new artifact\n\n**What**\n\nClaude Code now has a separate reason for refusing to publish an artifact. It applies when the permission check for the publish cannot finish and your organization requires a person to approve each new artifact. The message reads: \"Artifact publishes fail closed when their permission check cannot complete and the organization requires a person to approve each new artifact\". Before, only a general message about artifact actions failing closed was available.\n\n**Why**\n\nIf a publish is refused, the message now tells you that your organization's policy of approving each new artifact is involved.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}