You'll notice
Artifact publish now rejects file references into other artifacts, requiring a local copy instead
What
When publishing an artifact, the files parameter no longer accepts entries shaped like {artifact, path} — 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}.
Why
This 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.