Artifact publishing drops the live-files and custom-endpoint routes
Artifact publishing now always posts to one address, drops the live-doc and custom-endpoint routes, and liveFiles no longer triggers the multi-file path
Group of 2You'll noticeNo documentation foundInternal Changes
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.323,
Internal ChangesSection of the release
Unclear Whether liveFiles still does anything elsewhere is not stated.
What
Publishing an artifact means sending its content off to be published. The code that does this has been cut down.
One address: publishing no longer accepts a custom endpoint and always posts the content to /api/frame/deploy/direct.
Per-file maps: the publish function no longer takes per-file files maps.
Removed branches: the live-doc branch and the create-endpoint branch are gone, along with the error "create endpoint not available (404)".
Multi-file path: the branch that handles several files now runs only when files, removeFiles or a third list is non-empty. Setting liveFiles no longer sends a publish down that path, and some other lists that used to count no longer do.
Why
If you relied on live files, a custom publish address or the live-doc route when publishing artifacts, those routes are no longer there in this build. Publishes that add or remove files through files or removeFiles still go through the multi-file path.
