mono - chore: upgrading biome, rimraf, and types to latest

[jaredwray]

Please check if the PR fulfills these requirements

• Followed the Contributing and Code of Conduct guidelines.
• Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
mono - chore: upgrading biome, rimraf, and types to latest

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on routine maintenance by upgrading several key development dependencies to their latest versions. The primary goal is to ensure the project benefits from the most recent features, bug fixes, and security enhancements provided by these packages, thereby improving overall stability and developer experience. The changes are limited to dependency version bumps and the corresponding lockfile update.

Highlights

• Dependency Upgrades: Upgraded @biomejs/biome from ^2.3.14 to ^2.4.6, @types/node from ^25.2.3 to ^25.3.5, and rimraf from ^6.1.2 to ^6.1.3.
• Lockfile Synchronization: Synchronized the pnpm-lock.yaml file to reflect the updated direct and transitive dependencies, ensuring consistent package installations.

Changelog

• package.json
  • Updated @biomejs/biome from ^2.3.14 to ^2.4.6
  • Updated @types/node from ^25.2.3 to ^25.3.5
  • Updated rimraf from ^6.1.2 to ^6.1.3
• pnpm-lock.yaml
  • Updated lockfile entries for @biomejs/biome, @types/node, and rimraf to their new versions.
  • Removed @isaacs/balanced-match and @isaacs/brace-expansion entries, indicating resolution of dependencies.
  • Updated various transitive dependencies including acorn, balanced-match, brace-expansion, glob, lru-cache, minimatch, minipass, path-scurry, and undici-types.

Activity

• The pull request was created by jaredwray to upgrade development dependencies.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request upgrades several development dependencies. The upgrades for biome and rimraf are fine. However, the upgrade for @types/node is to a version from a mistaken and unpublished release series. I've left a critical comment with a suggestion to switch to a stable, published version of @types/node to ensure build stability.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (e15a744) to head (6d9f8af).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #169   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines         1067      1067           
  Branches       216       216           
=========================================
  Hits          1067      1067           

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