[RawToast]

Note

^{Cursor Bugbot is generating a summary for commit 52796de. Configure here.}

What this PR does

This PR updates the repository's development and runtime dependencies across the root workspace, examples package, and zenko package. Notable bumps include the OX toolchain (oxfmt, oxlint, oxlint-tsgolint), Turbo, TypeScript 5.9.3 → 6.0.2, tsdown 0.21.7 → 0.22.9, and Zod 4.3.6 → 4.4.3. The zenko package's peer dependency ranges are also widened to support TypeScript ^5 || ^6 || ^7 and pinned to Zod ^4.4.3.

[kanri-san]

Summary

This PR updates the repository's development and runtime dependencies across the root workspace, examples package, and zenko package. Notable bumps include the OX toolchain (oxfmt, oxlint, oxlint-tsgolint), Turbo, TypeScript 5.9.3 → 6.0.2, tsdown 0.21.7 → 0.22.9, and Zod 4.3.6 → 4.4.3. The zenko package's peer dependency ranges are also widened to support TypeScript ^5 || ^6 || ^7 and pinned to Zod ^4.4.3.

Changes

File	Change	Reason
package.json	Bumped root devDependencies: oxfmt 0.59.0, oxlint 1.74.0, oxlint-tsgolint 0.25.0, turbo 2.10.5.	Keeps the workspace's linter, formatter, and task runner on current versions.
packages/examples/package.json	Bumped zod to 4.4.3, @types/bun to 1.3.14, and typescript to 6.0.2.	Aligns example package runtime and type dependencies with the rest of the workspace.
packages/zenko/package.json	Bumped @types/bun to 1.3.14, tsdown to 0.22.9, and typescript to 6.0.2; widened typescript peerDependency to ^5 || ^6 || ^7 and pinned zod peerDependency to ^4.4.3.	Supports newer TypeScript consumers, updates the build toolchain, and pins the Zod peer requirement to the latest patch.
bun.lock	Regenerated lockfile reflecting the version bumps and transitive dependency updates (e.g., rolldown, rolldown-plugin-dts, dts-resolver, emnapi, yuku-* packages).	Ensures reproducible installs with the updated dependency tree.

---

Walkthrough by kanri

[coderabbitai]

Warning

Review limit reached

@RawToast, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b7abbf91-3d35-49d4-a45f-1da7760c43f5

📥 Commits

Reviewing files that changed from the base of the PR and between 23cd53d and 52796de.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• package.json
• packages/examples/package.json
• packages/zenko/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch updates

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[kanri-san]

Verdict

Status: REQUIRES CHANGES

Clean, well-scoped dependency bump with a consistent lockfile, but it must not ship as-is: the zod peerDependency was silently narrowed from ^4 to ^4.4.3 (C1) with no code requiring it — restore ^4 to avoid breaking consumers on zod 4.0–4.4.2. Afterwards, optionally address the untested typescript ^7 peer claim (C2) and the stale TypeScript requirement in AGENTS.md (C3).

2 findings below min severity (warning) were omitted from posting.

Inline comments: 1

---

Reviewed by kanri | 1 new inline comments

[kanri-san]

CRITICAL

The zod peerDependency was narrowed from "^4" to "^4.4.3", but nothing in packages/zenko/src or its generated output requires zod ≥ 4.4.3 — only long-standing zod 4.0+ APIs are used (z.object, z.string, z.union, z.discriminatedUnion, z.coerce, z.infer, safeParse, .optional, .transform, .refine, etc.). Narrowing the peer range silently breaks existing consumers on zod 4.0–4.4.2 with peer-dependency conflicts (npm ≥ 7 and pnpm error on conflicts), turning a routine dependency bump into an unintentional breaking change for the published package. Revert to "zod": "^4" unless a 4.4.3-specific API is actually introduced.

Fix with AI

Verify the issue still exists before applying this fix.

The zod peerDependency was narrowed from `"^4"` to `"^4.4.3"`, but nothing in `packages/zenko/src` or its generated output requires zod ≥ 4.4.3 — only long-standing zod 4.0+ APIs are used (`z.object`, `z.string`, `z.union`, `z.discriminatedUnion`, `z.coerce`, `z.infer`, `safeParse`, `.optional`, `.transform`, `.refine`, etc.). Narrowing the peer range silently breaks existing consumers on zod 4.0–4.4.2 with peer-dependency conflicts (npm ≥ 7 and pnpm error on conflicts), turning a routine dependency bump into an unintentional breaking change for the published package. Revert to `"zod": "^4"` unless a 4.4.3-specific API is actually introduced.

In packages/zenko/package.json, change the peerDependencies entry `"zod": "^4.4.3"` back to `"zod": "^4"` so consumers on any zod 4.x version remain supported. Regenerate the lockfile (bun install) afterwards.