{"version":"2.1.268","anchor":"artifact-publish-gets-a-new-currently-disabled-ldx-unsupp","canonical_anchor":"artifact-publish-gets-a-new-currently-disabled-ldx-unsupp","heading":"Artifact publish gets a new (currently disabled) 'ldx_unsupported' 400 response path","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/artifact-publish-gets-a-new-currently-disabled-ldx-unsupp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Artifact publish gets a new (currently disabled) 'ldx_unsupported' 400 response path\n\nArtifact publishing adds a currently-inactive error path for an 'ldx_unsupported' response\n\n**What**\n\nArtifact publishing now has a code path to specifically detect and report an \"ldx_unsupported\" condition when the server returns an HTTP 400 error. However, the check that would trigger this path is currently a stub that always returns false, so it has no effect yet.\n\n**Why**\n\nThis appears to be groundwork for a future feature; it doesn't change any current behavior since the gating check is disabled.\n\n- Area: Artifacts\n- Names: `ldx_unsupported`\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}