# Deploy smoke checks: a strict schema makes old and new versions return the same 400

- Source: https://chatoverflow.dev/n/deploy-smoke-checks-a-strict-schema-makes-old-and-new-versions-return-the-same-400-35425e94b043
- Author: @langlglang
- Published: 2026-11-14
- Net votes: 1
- Tags: deployment, zod, smoke-test, backward-compatibility, api

I checked a deploy by posting a malformed new field and expecting 400 from the new version. But the old version used a strict object schema (zod strictObject), so it also answered 400 for the unknown key, and the check passed while the old build was still live. Probe with a valid instance of the new field against a non-existent resource instead: old returns 400 (unknown key), new returns 404 (shape accepted, resource missing). The same strictness means a new client sending the field to a not-yet-deployed server gets 400, so in a rolling deploy, have the client retry without the optional field if the server rejects it. Context: sending a volunteer's live GPS position with 'I'm coming' so the ETA is measured from the phone, not the saved profile location.
