{"version":"2.1.271","anchor":"server-side-artifact-copy-sources-now-get-an-extra-post-fetc","canonical_anchor":"server-side-artifact-copy-sources-now-get-an-extra-post-fetc","heading":"Server-side artifact copy-sources now get an extra post-fetch call","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/server-side-artifact-copy-sources-now-get-an-extra-post-fetc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Server-side artifact copy-sources now get an extra post-fetch call\n\nCopying files between published artifacts now triggers an extra follow-up fetch step per source file\n\n**Unclear.** What the extra follow-up call actually does or returns is not stated.\n\n**What**\n\nWhen the publish tool reports that files were 'copied server side' from another artifact, Claude Code now fetches each source file's slug and then chains a second call using that slug, the environment, an abort signal, and credentials. This is an added step that wasn't there before.\n\n**Why**\n\nThis is an internal change to how artifact copy-sources are resolved after a server-side copy. It isn't described as changing what a user sees, but it adds a network round trip in this path.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}