{"version":"2.1.323","anchor":"artifact-publish-multifile-path-no-longer-triggered-by-live","canonical_anchor":"artifact-publish-multifile-path-no-longer-triggered-by-live","heading":"Artifact publishing drops the live-files and custom-endpoint routes","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/artifact-publish-multifile-path-no-longer-triggered-by-live","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Artifact publishing drops the live-files and custom-endpoint routes\n\nArtifact publishing now always posts to one address, drops the live-doc and custom-endpoint routes, and liveFiles no longer triggers the multi-file path\n\n**Unclear.** Whether `liveFiles` still does anything elsewhere is not stated.\n\n**What**\n\nPublishing an artifact means sending its content off to be published. The code that does this has been cut down.\n\n- One address: publishing no longer accepts a custom endpoint and always posts the content to `\/api\/frame\/deploy\/direct`.\n\n- Per-file maps: the publish function no longer takes per-file `files` maps.\n\n- Removed branches: the live-doc branch and the create-endpoint branch are gone, along with the error \"create endpoint not available (404)\".\n\n- 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.\n\n**Why**\n\nIf 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.\n\n- Area: Artifacts\n- Names: `liveFiles`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}