Update package dependencies

[RawToast]

Summary by CodeRabbit

• Chores

  • Updated development tooling and package manager versions across the project for maintenance and compatibility.
  • Updated dependency versions in example packages to keep runtime tooling and type definitions current.

• Releases

  • Promoted a package from beta to a stable 0.2.1 release.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Updates multiple package.json files to bump development and some package dependencies, and to move package version from a beta to stable; no runtime code or public API changes.

Changes

Cohort / File(s)	Summary
Root tooling & package manager package.json	Bumped devDeps: oxfmt 0.28.0→0.32.0, oxlint 1.43.0→1.47.0, oxlint-tsgolint 0.11.5→0.12.2, turbo 2.8.3→2.8.9; updated packageManager from bun@1.3.7→bun@1.3.9.
Examples package deps packages/examples/package.json	Bumped runtime/dev deps: @effect/platform 0.94.3→0.94.5, effect 3.19.16→3.19.17, undici 7.21.0→7.22.0, @types/bun 1.3.8→1.3.9.
Zenko package metadata packages/zenko/package.json	Released version changed 0.2.1-beta.1→0.2.1; bumped devDependencies["@types/bun"] 1.3.8→1.3.9.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Update dependencies and security issue #66: Overlapping dependency/version bumps in root and package package.json files.
• Update dependencies and typeaware linting #62: Related updates to devDependencies and package manager version.
• Swap prettier for oxfmt #55: Changes to formatting/lint tooling versions (oxfmt, oxlint) and packageManager.

Poem

🐰 Hopped through package.json lanes,

Bumped versions, synced the trains.
Bun and turbo, tidy and neat,
Dev tools updated, ready to fleet.
A rabbit's hop — small, precise, sweet.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Update package dependencies' accurately describes the main changeset, which exclusively contains dependency version updates across three package.json files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dependency-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 and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.45%. Comparing base (e3bb021) to head (0e13a9a).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #70   +/-   ##
=======================================
  Coverage   97.45%   97.45%           
=======================================
  Files          16       16           
  Lines        2277     2277           
=======================================
  Hits         2219     2219           
  Misses         58       58           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

🧹 Nitpick comments (1)

package.json (1)

23-27: Heads up on --max-warnings=0 with the oxlint jump.

oxlint moves four minor versions (1.43.0 → 1.47.0). New minor releases can introduce additional default-enabled rules, and the lint:check script uses --max-warnings=0, so any newly triggered rule will fail CI. Based on learnings, running bun check (which invokes the lint step) before merging is the recommended way to catch this early.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 23 - 27, The oxlint dependency was bumped (the
"oxlint" entry) and because the "lint:check" script uses the --max-warnings=0
flag, new default rules in 1.47.0 can cause CI to fail; before merging, run the
recommended preflight (run bun check locally which runs the lint step) to
surface any new lint errors, and if CI failures are unwanted either pin "oxlint"
back to the previous known-good version or relax/remove --max-warnings=0 in the
"lint:check" script so new minor-rule additions won’t break CI unexpectedly.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@package.json`:
- Around line 23-27: The oxlint dependency was bumped (the "oxlint" entry) and
because the "lint:check" script uses the --max-warnings=0 flag, new default
rules in 1.47.0 can cause CI to fail; before merging, run the recommended
preflight (run bun check locally which runs the lint step) to surface any new
lint errors, and if CI failures are unwanted either pin "oxlint" back to the
previous known-good version or relax/remove --max-warnings=0 in the "lint:check"
script so new minor-rule additions won’t break CI unexpectedly.