{"version":"2.1.277","anchor":"artifact-publish-rejects-remote-artifactpath-file-referen","canonical_anchor":"artifact-publish-rejects-remote-artifactpath-file-referen","heading":"Artifact publish rejects remote {artifact,path} file references, requires local copies","tier":"notice","area":"Artifact Publish","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/artifact-publish-rejects-remote-artifactpath-file-referen","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Artifact publish rejects remote {artifact,path} file references, requires local copies\n\nArtifact publish now rejects file references into other artifacts, requiring a local copy instead\n\n**What**\n\nWhen publishing an artifact, the `files` parameter no longer accepts entries shaped like `{artifact, path}` \u2014 a reference pointing into another artifact. Such entries now produce a validation error telling the caller to publish from a local copy instead, either a source path inside the artifact's root or an entry shaped like `{from, contentType}`.\n\n**Why**\n\nThis closes off publishing files by reference to another artifact, requiring an actual local copy of the content instead, which avoids depending on another artifact's contents at publish time.\n\n- Area: Artifact Publish\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}