Skip to content

mono - chore: centralizing dev dependencies to mono#1574

Merged
jaredwray merged 1 commit intomainfrom
mono---chore-centralizing-dev-dependencies-to-mono
Feb 6, 2026
Merged

mono - chore: centralizing dev dependencies to mono#1574
jaredwray merged 1 commit intomainfrom
mono---chore-centralizing-dev-dependencies-to-mono

Conversation

@jaredwray
Copy link
Owner

@jaredwray jaredwray commented Feb 6, 2026

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, ...)
mono - chore: centralizing dev dependencies to mono

@gemini-code-assist
Copy link

Summary of Changes

Hello @jaredwray, I'm Gemini Code Assist1! 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 streamlines the management of development dependencies across the monorepo by consolidating common tools like Biome and Vitest into the root package.json. This change reduces redundancy, simplifies future dependency updates, and ensures consistent versions of these tools across all sub-packages, thereby improving overall project maintainability.

Highlights

  • Dependency Centralization: Development dependencies such as @biomejs/biome, @vitest/coverage-v8, @vitest/spy, and vitest have been removed from the devDependencies sections of individual sub-packages and centralized in the root package.json.
  • Dependency Updates: The root package.json has seen updates for @biomejs/biome (to ^2.3.12), @vitest/coverage-v8 (to ^4.0.18), and vitest (to ^4.0.18).
  • New Root Dependency: The @vitest/spy package (^4.0.18) has been added to the devDependencies in the root package.json.
Changelog
  • package.json
    • Updated @biomejs/biome from ^2.3.11 to ^2.3.12
    • Updated @vitest/coverage-v8 from ^4.0.16 to ^4.0.18
    • Added @vitest/spy with version ^4.0.18
    • Updated vitest from ^4.0.16 to ^4.0.18
  • packages/benchmark/package.json
    • Removed @biomejs/biome from devDependencies
  • packages/cache-manager/package.json
    • Removed @biomejs/biome, @vitest/coverage-v8, @vitest/spy, and vitest from devDependencies
  • packages/cacheable-request/package.json
    • Removed @biomejs/biome, @vitest/coverage-v8, and vitest from devDependencies
  • packages/cacheable/package.json
    • Removed @biomejs/biome, @vitest/coverage-v8, and vitest from devDependencies
  • packages/file-entry-cache/package.json
    • Removed @biomejs/biome, @vitest/coverage-v8, and vitest from devDependencies
  • packages/flat-cache/package.json
    • Removed @biomejs/biome, @vitest/coverage-v8, and vitest from devDependencies
  • packages/memory/package.json
    • Removed @biomejs/biome, @vitest/coverage-v8, and vitest from devDependencies
  • packages/net/package.json
    • Removed @biomejs/biome, @vitest/coverage-v8, and vitest from devDependencies
  • packages/node-cache/package.json
    • Removed @biomejs/biome, @vitest/coverage-v8, and vitest from devDependencies
  • packages/utils/package.json
    • Removed @biomejs/biome, @vitest/coverage-v8, and vitest from devDependencies
Activity
  • No specific review comments or activity have been recorded for this pull request yet.
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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request successfully centralizes development dependencies such as @biomejs/biome, @vitest/coverage-v8, @vitest/spy, and vitest to the root package.json. This is a good practice for monorepos, promoting consistent dependency management and reducing redundancy across packages. The dependencies in the root package.json have also been updated to their latest versions. The changes are clear and align with the stated goal of the pull request.

@codecov
Copy link

codecov bot commented Feb 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (1b62a6c) to head (8cd5df6).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #1574   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           26        26           
  Lines         2444      2444           
  Branches       542       543    +1     
=========================================
  Hits          2444      2444           

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

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8cd5df6462

ℹ️ 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".

@jaredwray jaredwray merged commit 28607cc into main Feb 6, 2026
9 checks passed
@jaredwray jaredwray deleted the mono---chore-centralizing-dev-dependencies-to-mono branch February 6, 2026 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant