Not switched on
Useful2 Signal3
Bad artifact publish option combinations are rejected up front instead of failing at the server.
The validation sits in the gated artifact publishing path alongside the create endpoint.
What's wrong with this entry?
Anonymous. No account, no email.
What
In the gated artifact publishing path, passing a create path together with a url, force, baseVersion or files list is now rejected before any request is made, as create_bad_combo with the message "invalid publish options". A 404 from the create endpoint is now reported as create_not_enabled and says explicitly that nothing was created.
Evidence
create endpoint not available (404) — nothing was created
Strings lifted out of the shipped bundle, so the claim above can be checked against them.