Sourced from zod's releases.

v4.0.3

Commits:

• 5905a8d810eff6f4677e6aa9e557f92a676805cf Improve check-versions script
• f3e749b1b057a2cf0a0bce7e07abec4e0520e0f8 Remove global File interface
• 44a936cb77961e57a0988d8a3c63d9c71fce69ac 4.0.2
• 74006edd49e3fe8d74010090462859593c2bd1e2 Fix JSR provenance
• ff4af5e889d4ad7136a9cde7202b16261db5c83c 4.0.3
• ce573e8799f86e2f68307eba95c2d40fc92617b7 Update test badge
• 9a7161a976d6349f738c00cb6d6528c0407a65e8 Fix versions

v4.0.0

With this release, zod@4.0.0 has been published to npm. There were no code changes between 3.25.76 and 4.0.0!

Zod 4 has been stable for the past 6 weeks, but it was published inside zod@3.25.x on npm. this transitionary window gave the ecosystem time to incrementally support for Zod 4 (without dropping support for Zod 3). As there is now near-universal support for Zod 4 in the ecosystem, ths time feels right to finally put a bow on things 🎀

To upgrade to Zod 4:

npm upgrade zod@^4.0.0

If you’ve already migrated to Zod 4 using the subpaths, there are no changes required. however you can optionally simplify your imports (recommended)

// after upgrading to zod@4.0.0:
import * as z from "zod"; // Zod 4 (regular)
import * as z from "zod/mini" // Zod 4 Mini
// these still work, but are no longer needed

import * as z from "zod/v4";

import * as z from "zod/v4-mini":
// if you still need Zod 3

import * as z from "zod/v3"; // Zod 3

Library authors — if you've already implemented Zod 4 support according to the best practices outlined in the Library authors guide, bump your peer dependency to include zod@^4.0.0:

// package.json
{
  "peerDependencies": {
    "zod": "^3.25.0 || ^4.0.0"
  }
}

... (truncated)

• 9a7161a Fix versions
• ce573e8 Update test badge
• ff4af5e 4.0.3
• 74006ed Fix JSR provenance
• 44a936c 4.0.2
• f3e749b Remove global File interface
• 5905a8d Improve check-versions script
• b259211 4.0.1
• e899016 Support format in z.templateLiteral
• a7bd58a Remove when from params
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)