chore: upgrading cacheable and @cacheable/net to latest

[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 cacheable and @cacheable/net 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 performs routine dependency maintenance by upgrading the cacheable and @cacheable/net packages to their latest versions. This ensures the project benefits from the most recent features, bug fixes, and performance improvements provided by these core caching libraries and their transitive dependencies.

Highlights

• Dependency Upgrades: Updated cacheable to 2.3.3 and @cacheable/net to 2.0.6 in package.json.
• Lockfile Synchronization: Synchronized pnpm-lock.yaml to reflect the new dependency versions, including transitive updates for @cacheable/memory, @cacheable/utils, hashery, undici, and acorn.

🧠 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 @cacheable/net from ^2.0.4 to ^2.0.6.
  • Updated cacheable from ^2.3.2 to ^2.3.3.
• pnpm-lock.yaml
  • Updated @cacheable/net from 2.0.5 to 2.0.6.
  • Updated cacheable from 2.3.2 to 2.3.3.
  • Updated @cacheable/memory from 2.0.7 to 2.0.8.
  • Updated @cacheable/utils from 2.3.4 to 2.4.0.
  • Updated hashery from 1.4.0 to 1.5.0.
  • Updated undici from 7.16.0 to 7.22.0.
  • Updated acorn from 8.15.0 to 8.16.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 updates the @cacheable/net and cacheable dependencies to their latest patch versions. The changes are correct and update the lockfile accordingly. For improved long-term stability and to prevent unexpected issues from minor version updates, I've suggested changing the version range specifier from a caret (^) to a tilde (~). This restricts updates to patch-level changes, which are safer and lead to more predictable builds.

[codecov]

Codecov Report

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

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #120   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines          486       486           
  Branches        97       101    +4     
=========================================
  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.