Skip to content

chore: upgrading cacheable to 2.3.2#119

Merged
jaredwray merged 1 commit intomainfrom
chore-upgrading-cacheable-to-2.3.2
Feb 11, 2026
Merged

chore: upgrading cacheable to 2.3.2#119
jaredwray merged 1 commit intomainfrom
chore-upgrading-cacheable-to-2.3.2

Conversation

@jaredwray
Copy link
Contributor

@jaredwray jaredwray commented Feb 11, 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, ...)
chore: upgrading cacheable to 2.3.2

@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 focuses on a routine maintenance task: updating the project's core caching library, cacheable, to its latest patch version. This ensures the application benefits from the most recent bug fixes and minor improvements in the caching mechanism, maintaining stability and performance without introducing breaking changes. The associated lockfile has also been meticulously updated to guarantee consistent dependency resolution across environments.

Highlights

  • Dependency Upgrade: cacheable: The primary dependency cacheable has been upgraded from version 2.3.0 to 2.3.2 in package.json.
  • Lockfile Updates: The pnpm-lock.yaml file has been updated to reflect the new versions of cacheable, @cacheable/utils, @keyv/bigmap, keyv, and qified, along with their corresponding integrity hashes.
  • Sub-dependency Updates: Several sub-dependencies and their peer dependencies, such as @cacheable/utils (to 2.3.4), @keyv/bigmap (to 1.3.1), keyv (to 5.6.0), and qified (to 0.6.0), have been updated as part of the cacheable upgrade.

🧠 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 the cacheable dependency from ^2.3.0 to ^2.3.2.
  • pnpm-lock.yaml
    • Updated the cacheable package version from 2.3.1 to 2.3.2 and its integrity hash.
    • Updated the @cacheable/utils package version from 2.3.3 to 2.3.4 and its integrity hash.
    • Updated the @keyv/bigmap package version from 1.3.0 to 1.3.1 and its integrity hash.
    • Updated the keyv package version from 5.5.5 to 5.6.0 and its integrity hash.
    • Updated the qified package version from 0.5.3 to 0.6.0 and its integrity hash.
    • Adjusted dependency references within the snapshots section to reflect the new versions of @cacheable/utils, @keyv/bigmap, keyv, cacheable, and qified.
Activity
  • The pull request was opened by jaredwray with the title 'chore: upgrading cacheable to 2.3.2'.
  • The author confirmed adherence to contributing guidelines and code of conduct.
  • The author confirmed that tests for the changes have been added with 100% code coverage, indicating confidence in the upgrade's stability.
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.

@codecov
Copy link

codecov bot commented Feb 11, 2026

Codecov Report

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

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #119   +/-   ##
=========================================
  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.

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 upgrades the cacheable dependency from version ^2.3.0 to ^2.3.2. The changes in package.json and the corresponding updates in pnpm-lock.yaml are correct and consistent with the goal of this PR. This is a standard dependency update that helps keep the project's dependencies current. The changes look good.

@jaredwray jaredwray merged commit 2253b00 into main Feb 11, 2026
9 checks passed
@jaredwray jaredwray deleted the chore-upgrading-cacheable-to-2.3.2 branch February 11, 2026 16:39
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