-
Notifications
You must be signed in to change notification settings - Fork 4
✅ Catch-up: Next.js 16.1.6 (v16.1.0) #25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| { | ||
| "name": "@mrjasonroy/cache-components-cache-handler", | ||
| "version": "16.0.4", | ||
| "version": "16.1.0", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. While bumping the version to |
||
| "description": "Cache handler for Next.js 16+ with support for 'use cache' directive and Cache Components", | ||
| "author": "Jason Roy", | ||
| "license": "MIT", | ||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's great that this app is updated to
next: ^16.1.6. However, I noticed that theapps/redis-exampleapplication was not updated and still depends onnext: ^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-exampleshould be updated as well.