chore: upgrading vitest to 4.0.18

[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 vitest to 4.0.18

[gemini-code-assist]

Summary of Changes

Hello @jaredwray, 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 maintaining the project's health and stability by updating key development and runtime dependencies. The primary goal is to ensure compatibility, leverage the latest features, and benefit from bug fixes and performance improvements in these updated packages, particularly the testing framework Vitest.

Highlights

• Vitest Upgrade: The testing framework Vitest, along with its coverage plugin @vitest/coverage-v8, has been upgraded from version 4.0.15 to 4.0.18.
• Dependency Updates: Several other development dependencies including @swc/core, @types/node, and the runtime dependency @faker-js/faker have been updated to their latest minor or patch versions.
• Gitignore Modification: The pnpm-lock.yaml file has been removed from the .gitignore list, indicating a potential change in how pnpm lock files are managed or committed.

🧠 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

• .gitignore
  • Removed pnpm-lock.yaml from the list of ignored files.
• package.json
  • Updated @swc/core from ^1.15.3 to ^1.15.11.
  • Updated @types/node from ^25.0.0 to ^25.2.2.
  • Updated @vitest/coverage-v8 from ^4.0.15 to ^4.0.18.
  • Updated vitest from ^4.0.15 to ^4.0.18.
  • Updated @faker-js/faker from ^10.2.0 to ^10.3.0.

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 dependencies, including vitest. While the dependency updates are straightforward, there are two points to consider. First, the decision to version pnpm-lock.yaml (by removing it from .gitignore) is a good one, but it conflicts with the clean script in package.json which deletes this file. Second, the version of @types/node has been updated to a version that appears to be for a future, unreleased version of Node.js. This is risky as it can lead to runtime errors if APIs are used that are not present in the project's target Node.js version.

[codecov]

Codecov Report

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

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #115   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines          486       486           
  Branches       101       101           
=========================================
  Hits           486       486           

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 495079754c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".