fix: bump biome dependencies to latest

[tjazsilovsek]

Summary

• Bump @biomejs/js-api from 3.0.0 to 4.0.0
• Bump @biomejs/wasm-nodejs from 2.3.7 to 2.4.6

The bundled biome formatter (added in #1192) still uses biome 2.3.7. Projects using biome 2.4+ have config keys (e.g. assist, css.parser.tailwindDirectives) that cause applyConfiguration() to fail on 2.3.7, which silently falls back to biome defaults (double quotes instead of the project's configured single quotes). This leads to formatting conflicts on every lingo translation push.

Bumping to the latest biome versions ensures the bundled formatter can correctly parse and apply modern biome configs.

Summary by CodeRabbit

• Chores

  • Bumped @biomejs/js-api to 4.0.0
  • Bumped @biomejs/wasm-nodejs to 2.4.6
  • Updated manifest/declaration entries related to the dependency bumps

• Notes

  • Patch-level release; no observable functional or public API changes detected.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated two BiomeJS dependencies in the CLI package: @biomejs/js-api 3.0.0 → 4.0.0 and @biomejs/wasm-nodejs 2.3.7 → 2.4.6; added a changeset note. No other functional or public API changes detected.

Changes

Cohort / File(s)	Summary
CLI package manifest packages/cli/package.json	Bumped @biomejs/js-api to 4.0.0 and @biomejs/wasm-nodejs to 2.4.6.
Release notes / changeset .changeset/witty-owls-doubt.md	Added patch-level changeset noting the dependency bumps and lingo.dev patch designation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 I hopped through package.json to play,
Two versions nudged, then scurried away.
A tiny change, no fuss or tricks,
I left the tree with tidy ticks. 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description includes a clear summary and detailed rationale, but lacks the Changes, Testing, Visuals, and Checklist sections from the template.	Add a Changes section with bullet points, confirm testing status, and complete the Checklist section including changeset confirmation and breaking changes statement.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main change: bumping biome dependencies to their latest versions.
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

---

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.}

[AndreyHirsa]

Hi @tjazsilovsek! Thanks for the PR. Could you please add a changeset?

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

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

Inline comments:
In @.changeset/witty-owls-doubt.md:
- Line 5: Update the changelog entry in .changeset/witty-owls-doubt.md to avoid
the phrase “latest versions” by explicitly listing the bumped package versions
or a short user-visible description: replace the line "Bump `@biomejs/js-api` and
`@biomejs/wasm-nodejs` to latest versions" with either the exact version bumps
(e.g., "@biomejs/js-api 3.0.0 → 4.0.0" and "@biomejs/wasm-nodejs 2.3.7 → 2.4.6")
or a brief summary of the user-facing fix introduced by these bumps so the entry
remains accurate over time.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f9007e9b-5ae8-453a-ac97-34a676e2f70b

📥 Commits

Reviewing files that changed from the base of the PR and between 365743e and 14bc022.

📒 Files selected for processing (1)

• .changeset/witty-owls-doubt.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Use explicit versions instead of “latest versions”.

This changelog entry will age poorly: once Biome publishes newer releases, “latest versions” becomes inaccurate. Please spell out the actual bumps (@biomejs/js-api 3.0.0 → 4.0.0, @biomejs/wasm-nodejs 2.3.7 → 2.4.6) or describe the user-visible fix instead.

✏️ Suggested wording

-Bump `@biomejs/js-api` and `@biomejs/wasm-nodejs` to latest versions
+Bump `@biomejs/js-api` from 3.0.0 to 4.0.0 and `@biomejs/wasm-nodejs` from 2.3.7 to 2.4.6 to support newer Biome config keys

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Bump @biomejs/js-api and @biomejs/wasm-nodejs to latest versions
	---
	"@biomejs/js-api": patch
	"@biomejs/wasm-nodejs": patch
	---
	Bump `@biomejs/js-api` from 3.0.0 to 4.0.0 and `@biomejs/wasm-nodejs` from 2.3.7 to 2.4.6 to support newer Biome config keys

🤖 Prompt for AI Agents

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

In @.changeset/witty-owls-doubt.md at line 5, Update the changelog entry in
.changeset/witty-owls-doubt.md to avoid the phrase “latest versions” by
explicitly listing the bumped package versions or a short user-visible
description: replace the line "Bump `@biomejs/js-api` and `@biomejs/wasm-nodejs` to
latest versions" with either the exact version bumps (e.g., "@biomejs/js-api
3.0.0 → 4.0.0" and "@biomejs/wasm-nodejs 2.3.7 → 2.4.6") or a brief summary of
the user-facing fix introduced by these bumps so the entry remains accurate over
time.