{"version":"2.1.234","anchor":"publish-checks-the-server-s-answer-matches-the-artifact-you-","canonical_anchor":"publish-checks-the-server-s-answer-matches-the-artifact-you-","heading":"Publish checks the server's answer matches the artifact you targeted","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/publish-checks-the-server-s-answer-matches-the-artifact-you-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Publish checks the server's answer matches the artifact you targeted\n\nA publish response naming a different artifact than yours is now rejected rather than accepted.\n\n**What**\n\nDeploy 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.\n\n**Details**\n\n- 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.\n- 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_mismatch` event.\n\n**Evidence**\n\n`the server answered for a different artifact than the one targeted, so its answer was not adopted`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}