{"version":"2.1.273","anchor":"artifactpublish-permission-and-result-building-refactor","canonical_anchor":"artifactpublish-permission-and-result-building-refactor","heading":"Artifact\/'publish' permission and result-building refactor","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/artifactpublish-permission-and-result-building-refactor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Artifact\/'publish' permission and result-building refactor\n\nInternal refactor of artifact-publish permission checks and result assembly, no visible behavior change\n\n**What**\n\nThe code behind publishing artifacts was reworked internally in two areas: the read-permission checks that guard against reading from under a symlinked or redirected base path, and the assembly of deploy results (warnings, embedded content, manifest and live file paths, and lists of newly-live or reseeded files). The visible messages, such as 'root: reading from under ... is blocked by a Read permission rule' and 'plus N file(s) copied server side from ...', are unchanged.\n\n**Why**\n\nThis appears to be a behind-the-scenes cleanup, largely variable renaming from code minification, rather than a change to how artifact publishing behaves or what you see.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}