chore(deps): bump zod from 4.6.5 to 4.6.6

[dependabot]

Bumps zod from 4.6.5 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

Commits

• 9c21983 ci: stage at verbose so a failed OIDC token exchange says why
• 529f78d 4.6.6
• a0ebf97 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 tiles
• 8fb2faf docs: crop the Code for Japan logo and list it first in bronze
• b2ef983 docs: add Code for Japan to bronze sponsors
• 74304ce release: stage npm versions instead of publishing them (#6622)
• 34a626f docs: tighten the z.locales tree-shaking note
• Additional commits viewable in compare view

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 @dependabot rebase.

---

Dependabot commands and options

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 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)

[claude]

I reviewed this PR and found no bugs. It's worth a human look anyway, because the lockfile pulls in more than the title says and zod's own release notes describe a recent credential compromise.

What was reviewed:

• The package.json specifier and the pnpm-lock.yaml importer agree: both are ^4.6.6 and resolve to 4.6.6. No source files changed.
• The lockfile also moves four packages the title doesn't mention: postcss 8.5.28 -> 8.5.30, nanoid 3.3.19 -> 3.3.20, source-map-js 1.2.1 -> 1.2.2 (all reached through vite) and @ napi-rs/wasm-runtime 1.2.4 -> 1.2.5 (optional, rolldown wasm32-wasi). Each has a new integrity hash, and I couldn't check those hashes against the registry here.
• zod's 4.6.6 notes say a compromised git credential was used to push malicious commits to main, which were later removed from its history. They also say the npm provenance for this release names 284243fb, which is no longer on main. Someone should confirm the published 4.6.6 tarball and the extra transitive bumps before merging.

Extended reasoning...

The change touches only package.json and pnpm-lock.yaml: it bumps the runtime dependency zod from 4.6.5 to 4.6.6, moves four other packages to new versions, and adds deprecation notes to the yuku-codegen and yuku-parser 0.10.2 binding entries. There is no application code, so the risk is entirely supply chain. Two facts decided defer over approve. First, the lockfile changes more than the one dependency the title names. Second, zod's release notes for this version say the repo had a credential compromise and that the npm provenance points to a commit that has since been rewritten out of main. Neither can be checked from this offline checkout.