chore: upgrading biome and types

[jaredwray]

Please check if the PR fulfills these requirements

• Followed the Contributing guidelines and Code of Conduct
• 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, ...)
chore: upgrading biome and types

[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 performs routine maintenance by updating key development dependencies. It upgrades the Biome formatter and linter to its latest version and refreshes the Node.js type definitions. These updates ensure the project leverages the most recent improvements, bug fixes, and enhanced type safety provided by these tools, contributing to a more robust and maintainable codebase.

Highlights

• Dependency Upgrades: Upgraded the @biomejs/biome development dependency to version 2.4.6.
• Type Definition Updates: Updated the @types/node development dependency to version 25.4.0.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• package.json
  • Updated @biomejs/biome from ^2.3.14 to ^2.4.6.
  • Updated @types/node from ^25.3.3 to ^25.4.0.
• pnpm-lock.yaml
  • Updated lockfile entries for @biomejs/biome and its associated CLI packages to version 2.4.6.
  • Updated lockfile entries for @types/node to version 25.4.0.
  • Adjusted integrity hashes and dependency references to reflect the updated versions.

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 @biomejs/biome and @types/node dependencies. The upgrade for @biomejs/biome is a standard minor update. However, the @types/node dependency is being upgraded to another pre-release version (^25.4.0). While this might be intentional, using pre-release versions for type definitions can be risky. I've added a comment suggesting to pin @types/node to a stable version that aligns with the project's specified Node.js engine version for better stability and type consistency.

[gemini-code-assist]

The version of @types/node is set to ^25.4.0, which corresponds to a pre-release (next) version. The engines field in this package.json specifies a Node.js version of >=20.12.0. Using a next version for type definitions can introduce instability or types that are not yet available in the specified Node.js runtime. It is recommended to use a stable version of @types/node that matches the major version of your Node.js runtime to ensure type safety and stability. For example, you could use ^20.12.0 to align with your engines configuration.

Suggested change

	"@types/node": "^25.4.0",
	"@types/node": "^20.12.0",

[codecov]

Codecov Report

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

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #125   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines          477       477           
  Branches        95        99    +4     
=========================================
  Hits           477       477           

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