[dependabot]

Bumps zod from 4.6.5 to 4.6.7.

Release notes

Sourced from zod's releases.

v4.6.7

Commits:

• b500a2ee95134f81d74da7911d7378dd2853d042 4.6.7

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

• b500a2e 4.6.7
• 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)
• 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: needs changes before merge.

What this changes

This PR consolidates Better Auth’s JOSE dependency from 6.2.12 onto the existing 6.2.13 resolution.

Example: Installing the Worker’s Better Auth dependencies

• Before: Better Auth resolves jose 6.2.12 alongside the application’s jose 6.2.13.
• After: Both resolve jose 6.2.13; Zod resolutions remain unchanged.

Review scores

Measure	Result	What it means
Overall readiness	🦐 gold shrimp (3/6)	The minimal dependency patch has passing integration checks and no identified runtime defect, but validation remains harness-based and the advertised dependency update is inaccurate.
Proof confidence	🦐 gold shrimp (3/6)	This Dependabot maintenance PR is outside the contributor live-proof gate; exact-head CI passes, and existing Worker tests exercise real Better Auth and D1 with provider HTTP replaced.
Patch quality	🐚 platinum hermit (4/6)	1 actionable review finding remain.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: The authentication dependency graph retains two compatible JOSE patch versions.
Reason: The actual patch finishes a small compatible dependency consolidation without adding configuration, APIs, schema changes, or another dependency source.

Merge readiness

⛔ Needs changes before merge - 1 item remains

Keep open: this PR contains a distinct JOSE dependency update that is absent from main, but its Zod update claim does not match the patch.

Priority: P3
Reviewed head: 1886ecb93e001e80bbd8ce6dd3a7df2834fe1807

Before merge

• Correct the dependency update claimed by this PR (P3) - The body claims a Zod 4.6.5-to-4.6.7 update, but this hunk and the rest of the patch only update JOSE. An installation still gives @cloudflare/vitest-plugin 1.4.6 its exactly pinned Zod 4.6.5, while application Zod was already 4.6.7. Replace the Zod update claim and release notes with the actual JOSE consolidation so reviewers do not approve this as delivering an update it leaves unchanged.

Findings

• [P3] Correct the dependency update claimed by this PR — pnpm-lock.yaml:2983

Agent review details

How this fits together

The workspace lockfile selects dependencies installed for the Worker, dashboard, SDKs, and tooling; the changed JOSE resolution is consumed by Better Auth in the Worker’s authentication stack.

flowchart LR
  A[Workspace manifests] --> B[pnpm lockfile]
  B --> C[Worker dependencies]
  C --> D[Better Auth]
  D --> E[JOSE cryptography]
  D --> F[Authentication responses]

Loading

Technical review

Best possible solution:

Retain the focused JOSE consolidation and accurately describe it without overriding Cloudflare’s exact Zod dependency.

Do we have a high-confidence way to reproduce the issue?

No runtime bug is reported; source inspection establishes that JOSE changes while both Zod versions and their consumers remain unchanged.

Is this the best way to solve the issue?

Reusing the existing JOSE 6.2.13 resolution is a minimal maintenance change, whereas forcing Zod 4.6.7 would override an upstream exact dependency and expand the scope.

Full review comments:

• [P3] Correct the dependency update claimed by this PR — pnpm-lock.yaml:2983
  The body claims a Zod 4.6.5-to-4.6.7 update, but this hunk and the rest of the patch only update JOSE. An installation still gives @cloudflare/vitest-plugin 1.4.6 its exactly pinned Zod 4.6.5, while application Zod was already 4.6.7. Replace the Zod update claim and release notes with the actual JOSE consolidation so reviewers do not approve this as delivering an update it leaves unchanged.
  Confidence: 1

Overall correctness: patch is correct
Overall confidence: 0.96

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 6eb82bab1edf.

Provenance checked

• Better Auth’s JOSE resolution keeps the original intent (f7f30f3: The compatible dependency refresh in build(deps): refresh compatible dependencies and patch Undici #87 selected JOSE 6.2.12; build(deps): patch Node runtimes and refresh compatible dependencies #161 subsequently moved the direct application dependency to 6.2.13 while retaining compatible transitive resolutions.)

Testing

Proof path: in-process harness.

Security

None.

Evidence

Acceptance criteria:

• git diff --no-ext-diff --no-textconv --no-renames 6eb82ba 1886ecb -- pnpm-lock.yaml
• gh api repos/openclaw/krillswitch/pulls/168 --jq '{title,body,head:.head.sha}'
• git status --porcelain=v1

What I checked:

• Pinned patch changes JOSE only: The complete introduced diff removes jose 6.2.12 and redirects Better Auth and its peer-qualified snapshots to the already-present jose 6.2.13. No Zod entry changes. (pnpm-lock.yaml:2983, 1886ecb93e00)
• Main still contains the distinct JOSE resolution: GitHub’s main ref remains 6eb82ba. Its application dependency already resolves JOSE 6.2.13, but Better Auth still resolves 6.2.12; the PR is therefore not wholly implemented on main. (pnpm-lock.yaml:2986, 6eb82bab1edf)
• Remaining Zod version is an upstream exact pin: The npm manifest for @cloudflare/vitest-plugin 1.4.6 declares zod exactly 4.6.5, matching the unchanged lockfile consumer. A compatible transitive refresh cannot replace that exact pin with 4.6.7.
• Dependency history supports compatible maintenance: Merged build(deps): patch Node runtimes and refresh compatible dependencies #161 refreshed JOSE and retained the two-day cooldown; build(deps): bump the production group across 1 directory with 3 updates #145 previously updated application Zod to 4.6.7. Lockfile history also shows repeated dependency maintenance by steipete and workspace/auth contributions by vincentkoc. Some broader historical git-show reads encountered unavailable blobs; scoped lockfile history and blame were readable. (pnpm-lock.yaml:99, 7d6ec50510d6)
• Actual dependency change and supply-chain inspection: The runtime dependency changes from JOSE 6.2.12 to 6.2.13, making its published contract relevant. Upstream source changes preserve underlying error causes and align terminology; inspected verification failures still reject. The npm 6.2.13 integrity matches the retained lockfile hash, and its published manifest has no dependencies or lifecycle scripts. (src/lib/jws_verify.ts, 724ba24b5aaa)
• Exact-head checks and discussion: The reviewed head has 13 successful checks and two skipped checks, with no failures. Full discussion contains only ClawSweeper status comments and no maintainer direction or behavior artifacts. The supplied primary-body identity is cac1edce05ee4dad2577f68523f8fd3c356c4d179c127245bba3c2ecf42b1d97. (1886ecb93e00)

Likely related people:

• Peter Steinberger: Raw commit 089057e adds pnpm-lock.yaml:3017 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 089057ed8c74; files: pnpm-lock.yaml)
• Josh Avant: Raw commit 7d6ec50 adds pnpm-lock.yaml:99 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: medium; commits: 7d6ec50510d6; files: pnpm-lock.yaml)
• Vincent Koc: Raw commit 870196f adds pnpm-lock.yaml:91 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: medium; commits: 870196ff7ff8; files: pnpm-lock.yaml)

Labels

Label changes:

• add P3: This is a compatible dependency consolidation with an inaccurate update claim and no demonstrated runtime regression.
• add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🐚 platinum hermit.
• add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action.

Label justifications:

• P3: This is a compatible dependency consolidation with an inaccurate update claim and no demonstrated runtime regression.
• rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🐚 platinum hermit.
• status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action.

Rating scale

6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed October 24, 2026, 2:33 AM ET / 06:33 UTC.

[dependabot]

Looks like zod is no longer updatable, so this is no longer needed.