{"version":"2.1.273","anchor":"artifact-publish-flow-adds-a-bypass-path-around-the-copy-so","canonical_anchor":"artifact-publish-flow-adds-a-bypass-path-around-the-copy-so","heading":"Artifact publish flow adds a bypass path around the 'copy source unverified' approval check","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/artifact-publish-flow-adds-a-bypass-path-around-the-copy-so","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Artifact publish flow adds a bypass path around the 'copy source unverified' approval check\n\nPublishing copied artifact files can now skip the unverified-copy-source approval check under certain conditions\n\n**Unclear.** What specifically triggers the bypass condition, and how it differs from the existing approval check, isn't established by the evidence.\n\n**What**\n\nWhen publishing files that were copied from another artifact, Claude Code normally requires prior approval to read the copy source, and otherwise throws a `copy_source_unverified` error and records a `copies_unpinned` telemetry event. There is now an additional condition, checked with a permission function called with `copySource: true` and action `ask`, that when true skips both the error and the telemetry event.\n\n**Why**\n\nThe finding doesn't say what triggers this bypass condition in practice, so it's unclear when publishing will now proceed without the usual unverified-copy-source check.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}