GeezerVison is showing github.com — Build(deps): Bump zod from 3.25.76 to 4.6.6 in /npm/socket-patch by dependabot[bot] · Pull Request #1702 · SocketDev/socket-patch
Conversation
dependabot
Bot
commented
on behalf of github
Oct 23, 2026
•
edited by mikolalysenko
Loading
Uh oh!
There was an error while loading. Please reload this page.
Bumps zod from 3.25.76 to 4.6.6.
Release notes
Sourced from zod's releases.
v4.6.6
Six malicious commits pushed to main on September 21 with a compromised git credential were reverted the same day in #6620 and have since been removed from the history of main. None were ever published to npm. The npm provenance for 4.6.6 names 284243fb, the pre-rewrite copy of 9c219833 with identical contents.
Commits:
- 0cd3af5e9f50ad11bbcd4407a46a21b8848ba574 docs: load the en locale directly in Zod Mini
- 9d5e60f162997b764b40d45aa02481888db50dea docs: import locales from zod/locales, not z.locales
- 34a626f307871ecbb0123947559328dc52ed5e3e docs: tighten the z.locales tree-shaking note
- 74304ce5b5796b5edb9a88ceb8e170b6ea3e82df release: stage npm versions instead of publishing them (#6622)
- b2ef983e0711ff6517d6020b021071e2e5653efa docs: add Code for Japan to bronze sponsors
- 8fb2faf0584828a6a027d8279db36f6f52784462 docs: crop the Code for Japan logo and list it first in bronze
- bacad518c41610d654658172d325874bf0ee6290 docs: square the Code for Japan logo to match the other bronze tiles
- c42596bd1c87e941d7241d10e012c5c196adcc10 release: hold the run on the release-approval environment until the staged versions are approved (#6638)
- a2ba4a67986a3e6b2b131be30084a2f460d9ea67 fix(types): declare record output and input as members, not base type arguments (#6645)
- a0ebf970f2d752e5f58527cd2942ff48be4f46bd fix(v4): check array, set and map size bounds before parsing elements (#6652)
- 529f78dd9431b07f49647fee3aa0819b3f8b66b7 4.6.6
- 9c219833c3a3764fa1f1ea9c5ecec8254a63c0b1 ci: stage at verbose so a failed OIDC token exchange says why
v4.6.5
Commits:
- d2b135cfb7a3582b9eb515756b9166bcb9521f4a docs: add the 4.6.x patch highlights to the 4.6 post
- f1448f7cee00df9fe1e9ad84a000aa1828cc8bc1 docs: fold the 4.6.x patch highlights into the 4.6 post's own sections
- de65a5cb39ed22a507fac935788f718fa88d104f docs: lead the properties section with the check and add a Zod Mini tab (#6598)
- 56222cd1532c07bcb91b67df529cab4c0a215330 feat(instanceof): key the .properties() shape off the instance type (#6600)
- ca0229a404818290e6cdcfefcd7eb2d04bcbb543 Revert "feat: add z.currencyCode() over a vendored ISO 4217 list, refreshed weekly by CI (#6595)"
- cc4cd4ee9c52fcaa10964e48cc144541e41a5ed9 Revert "Revert "feat: add z.currencyCode() over a vendored ISO 4217 list, refreshed weekly by CI (#6595)""
- 0f3f5ee3ca56c7574bf849e54f79e9a6e02562ee 4.6.5
- 59bbc03e10c636b9eb3c393dfeb552819774ec21 chore: re-pin the integration peers to the workspace zod after the 4.6.5 bump
v4.6.4
A patch on top of 4.6.3.
d6bc1e30 feat: add z.currencyCode() over a vendored ISO 4217 list, refreshed weekly by CI (#6595)ad32d751 perf: z.url() rejects an invalid URL with URL.canParse() instead of a throwing constructor, about 50x faster; fewer allocations on the validation path (#6588)2bb08717 chore: re-pin the integration peers to the workspace zod after the 4.6.4 bumpf6e1701a chore(deps): bump next to 15.5.25 and vite to 7.3.6 (#6153)
v4.6.3
A patch on top of 4.6.2.
413cce9a fix(v4): make z.properties() a check again (#6594) — removes the standalone z.properties() schema from 4.6.0; z.instanceof().properties() and .check(...z.properties()) are unchanged75d63ee1 docs: show only the .properties() method form in the 4.6 post46da9572 docs: match the error-message examples to what the parsers emit
v4.6.2
A patch on top of 4.6.1.
... (truncated)
Commits
9c21983 ci: stage at verbose so a failed OIDC token exchange says why529f78d 4.6.6a0ebf97 fix(v4): check array, set and map size bounds before parsing elements (#6652)a2ba4a6 fix(types): declare record output and input as members, not base type argumen...c42596b release: hold the run on the release-approval environment until the staged ve...bacad51 docs: square the Code for Japan logo to match the other bronze tiles8fb2faf docs: crop the Code for Japan logo and list it first in bronzeb2ef983 docs: add Code for Japan to bronze sponsors74304ce release: stage npm versions instead of publishing them (#6622)34a626f docs: tighten the z.locales tree-shaking note- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for zod since your current version.
[[Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=zod&package-manager=npm_and_yarn&previous-version=3.25.76&new-version=4.6.6)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot 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 ·@·d·ependabot r·ebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
·@·d·ependabot r·ebase will rebase this PR·@·d·ependabot r·ecreate will recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency·@·d·ependabot i·gnore t·his 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)·@·d·ependabot i·gnore t·his 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)·@·d·ependabot i·gnore t·his dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.
Generated by Claude Code
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
test_release_lint_catches_npm_dependency_drift rewrote "zod": "3.25.76"
to inject drift, so the zod 4.6.6 bump made the replace a no-op and the
lint passed. Read the pinned version from package.json so the test keeps
injecting real drift whatever zod version is pinned.
Co-Authored-By: Claude <[email protected]>
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Bugbot couldn't run
Restrict Access is on for this team. The pull request's author, or the person who launched the agent, is blocked by the team's Restrict Access list.
A team admin can change the list in the Cursor dashboard.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Burn-down agent: CI is green, but this PR needs a human decision because Bugbot can't review it.
- Head:
d372cfeecc8a94083e37e462aa71cad2abae677f
- Fix pushed:
lint-ecosystems failed because test_release_lint_catches_npm_dependency_drift hardcoded "zod": "3.25.76". After the bump its replace did nothing, so no drift was injected. The test now reads the pinned zod version from package.json. All 369 scripts/tests pass locally.
- CI: 35/35 green (19 skipped) on the current head.
- zod 3 → 4 is a major bump.
npx tsc --noEmit passes on npm/socket-patch with zod 4.6.6, and src/schema/manifest-schema.ts only uses z.object/z.record(k, v)/z.string().uuid()/z.array/.optional(), which all still exist in v4. .uuid() is deprecated in v4 in favour of z.uuid() but still works.
- Lockfile: dependabot also added the 14
@socketsecurity/socket-patch-* platform entries at 5.0.1. release-lint accepts these ("npm lock OK").
Question: Bugbot refuses to run here ("Restrict Access is on for this team"). The PR author is dependabot. Should this go to Ready for review without a Bugbot pass, or will a maintainer trigger Bugbot (or allow bot-authored PRs)?
Generated by Claude Code
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|