A publish response naming a different artifact than yours is now rejected rather than accepted.
What's wrong with this entry?
Deploy responses are now validated against a strict schema, and a response naming a different artifact than the one you published is rejected instead of adopted.
- Slug and version are pattern-checked and the read/shared visibility fields are normalized, replacing scattered field checks; any malformed response now produces one consistent error message.
- A mismatched slug is refused with "the server answered for a different artifact than the one targeted, so its answer was not adopted" and records a
deploy_slug_mismatchevent.
the server answered for a different artifact than the one targeted, so its answer was not adopted
Strings lifted out of the shipped bundle, so the claim above can be checked against them.