Repository navigation
chore: raise minimum supported Next.js, React and Node.js versions - #670
Merged
Merged
Conversation
Next.js 15 and earlier, and Node.js 20 and earlier, are end-of-life or about to be. Require the versions that are still supported, matching what CI tests. BREAKING CHANGE: next-cloudinary now requires Next.js 16, React 18.2 or 19, and Node.js 22 or later. Projects on older versions can stay on v6.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PaulBoye-py
marked this pull request as ready for review
October 12, 2026 20:33
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Raises the minimum supported versions for v7, as proposed in this comment on #523.
^12to^16^16^17to^19^18.2.0 || ^19engines)>=22Support dates are from endoflife.date (Next.js, React, Node.js).
Projects on older versions can stay on v6. The first commit includes a
BREAKING CHANGEfooter so this appears in the v7 release notes.Not included: the docs site still runs Next.js 14 and React 18. It still builds, since peer dependency mismatches only produce warnings, so upgrading it can be a separate follow-up.
Issue Ticket Number
No separate issue. Part of the v7.0.0 scope discussed in #523.
Type of change
Checklist
Testing
pnpm install --frozen-lockfileworks (the lockfile doesn't change).engines.nodefield" suggestion is resolved).peerDependenciesandenginesvalues.