chore(deps): bump zod from 4.5.2 to 4.5.4 - #82
Conversation
Bumps [zod](https://github.com/colinhacks/zod) from 4.5.2 to 4.5.4. - [Release notes](https://github.com/colinhacks/zod/releases) - [Commits](colinhacks/zod@v4.5.2...v4.5.4) --- updated-dependencies: - dependency-name: zod dependency-version: 4.5.4 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
No changeset foundThis PR does not add a changeset, so it will not appear in the changelog or trigger a release. If the change is user-facing, add one: pnpm changesetPick a bump (patch / minor / major) and write the changelog entry in our usual voice ("Added X... Thanks to @you. Closes #123."), then commit the generated If this PR is docs-only or a chore that needs no release note, you can ignore this — or run |
nc-review: nothing to raiseDependabot bumps zod from 4.5.2 to 4.5.4 in pnpm-lock.yaml only. The package.json is untouched, so the published peerDependency range ( 🔴 blocking · 🟠 a reviewer would ask for a change · ⚪ optional Automated code review — correctness, security, design, tests, plus duplicates and scope. A human still decides; this is not a substitute for review and is not exhaustive. The required status checks separately cover lint, formatting, types, unused dependencies, the test suite and the build. This bot never merges. Maintainers can rerun with |
Bumps zod from 4.5.2 to 4.5.4.
Release notes
Sourced from zod's releases.
Commits
e8e206f4.5.484e416ffix(v4): stop the cycle walk from firing a default factory (#6500)1a161024.5.3eab51fffix(v4): emit record numeric keys as strings in toJSONSchema (#6497)7e24a24docs(blog): drop the reading time and put a GitHub link in the navbare3a695bdocs(v4): record the email regex and container output-shape findings under Open99fce39bench(v4): z.compile() against zod-compiler (#6499)87d6464fix(docs): drop the OG description when the title wraps past two linese6b6ab3docs(blog): widen the z.compile example to a 20-property schemaDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)