Nothing to try yet
No documentation found
Artifact publishing adds a currently-inactive error path for an 'ldx_unsupported' response
What
Artifact 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.
Why
This appears to be groundwork for a future feature; it doesn't change any current behavior since the gating check is disabled.
Names in the bundleldx_unsupported