You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Artifact PublishArea: what it touches
ImprovementsKind: in v2.1.277,
ImprovementsSection of the release
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.
