Skip to content

✅ Catch-up: Next.js 16.1.6 (v16.1.0)#25

Merged
mrjasonroy merged 1 commit intomainfrom
catch-up-16.1.0
Feb 4, 2026
Merged

✅ Catch-up: Next.js 16.1.6 (v16.1.0)#25
mrjasonroy merged 1 commit intomainfrom
catch-up-16.1.0

Conversation

@mrjasonroy
Copy link
Copy Markdown
Owner

Catch-up Release for Next.js 16.1.6

This release updates the cache handler to support Next.js 16.1.x.

Changes

  • ⬆️ Updated Next.js to 16.1.6
  • 📦 Bumped package version to 16.1.0

Test Results

  • ✅ Memory cache tests: PASSED (44 tests)
  • ✅ Redis cache tests: PASSED (44 tests)

Automation

After merge:

  1. Git tag v16.1.0 will be created
  2. Package will be published to npm

Auto-generated by catch-up-release workflow

- Updated Next.js to 16.1.6
- Updated package version to 16.1.0
- All tests passing

Co-Authored-By: GitHub Actions <github-actions[bot]@users.noreply.github.com>
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @mrjasonroy, 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 performs a crucial catch-up release, updating the project's Next.js dependencies to version 16.1.6. The core purpose is to ensure that the custom cache handler remains fully compatible and optimized for the latest Next.js runtime, thereby maintaining application stability and performance. This update also involves a version bump for the cache handler package itself.

Highlights

  • Next.js Version Update: The Next.js dependency has been updated across the project's test applications to version 16.1.6, ensuring compatibility with the latest Next.js features and fixes.
  • Cache Handler Version Bump: The @mrjasonroy/cache-components-cache-handler package version has been incremented to 16.1.0 to reflect its updated support for Next.js 16.1.x.
  • Dependency Lockfile Update: The pnpm-lock.yaml file has been comprehensively updated to reflect the new Next.js version and its associated transitive dependencies, including various @next/swc-* packages and baseline-browser-mapping.

🧠 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
  • apps/e2e-test-app/package.json
    • Updated the next dependency from ^16.0.1 to ^16.1.6.
  • apps/legacy-cache-test/package.json
    • Updated the next dependency from ^16.0.1 to ^16.1.6.
  • packages/cache-handler/package.json
    • Incremented the package version from 16.0.4 to 16.1.0.
  • pnpm-lock.yaml
    • Updated the next dependency version from 16.0.1 to 16.1.6 for various importers.
    • Added new resolution entries for @next/env@16.1.6 and several @next/swc-* packages corresponding to Next.js 16.1.6.
    • Introduced baseline-browser-mapping@2.9.19 as a new dependency.
    • Updated the detailed resolution for next@16.1.6, including its dependencies and peer dependencies.
Activity
  • This pull request was auto-generated by a catch-up-release workflow.
  • All 44 memory cache tests passed successfully.
  • All 44 Redis cache tests passed successfully.
  • Upon merging, a Git tag v16.1.0 will be created.
  • The updated package will be automatically published to npm after the merge.
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
Copy Markdown

@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 PR updates dependencies to support Next.js 16.1.x. The changes are mostly correct, but I've identified a couple of inconsistencies regarding dependency versions across the workspace that should be addressed for completeness and security. Please see my detailed comments.

"@mrjasonroy/cache-components-cache-handler": "workspace:*",
"ioredis": "^5.4.1",
"next": "^16.0.1",
"next": "^16.1.6",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

high

It's great that this app is updated to next: ^16.1.6. However, I noticed that the apps/redis-example application was not updated and still depends on next: ^16.0.1. The lockfile shows this resolves to a version that is deprecated due to a security vulnerability. For consistency and security across the project, apps/redis-example should be updated as well.

{
"name": "@mrjasonroy/cache-components-cache-handler",
"version": "16.0.4",
"version": "16.1.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

While bumping the version to 16.1.0 to reflect support for Next.js 16.1.x is correct, the package's own development environment should also be aligned. To ensure the package is developed and tested against this version, please consider adding next: "^16.1.6" to the devDependencies in this file. This makes the dependency explicit and avoids inconsistencies where an older version might be used during development.

@mrjasonroy mrjasonroy merged commit ec31df6 into main Feb 4, 2026
7 checks passed
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