Skip to content

chore: raise minimum supported Next.js, React and Node.js versions - #670

Merged
PaulBoye-py merged 2 commits into
betafrom
chore/raise-version-floors
Oct 12, 2026
Merged

PaulBoye-py merged 2 commits into
betafrom
chore/raise-version-floors

Conversation

@PaulBoye-py

Copy link
Copy Markdown
Collaborator

Description

Raises the minimum supported versions for v7, as proposed in this comment on #523.

v6 v7 (this PR) Why
Next.js (peer) ^12 to ^16 ^16 Next.js 15 reaches end-of-life on October 21, 2026, before v7 ships, and 12–14 already have. CI only tests Next.js 16.
React (peer) ^17 to ^19 ^18.2.0 || ^19 The same range Next.js 16 itself accepts.
Node.js (engines) not set >=22 Node.js 20 reached end-of-life on April 30, 2026.
CI test matrix Node 20, 22 Node 22, 24 Tests now run on the Node.js versions we support.

Support dates are from endoflife.date (Next.js, React, Node.js).

Projects on older versions can stay on v6. The first commit includes a BREAKING CHANGE footer 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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Fix or improve the documentation
  • This change requires a documentation update

Checklist

  • I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
  • I have created an issue ticket for this PR
  • I have checked to ensure there aren't other open Pull Requests for the same update/change?
  • I have performed a self-review of my own code
  • I have run tests locally to ensure they all pass
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes needed to the documentation

Testing

  • pnpm install --frozen-lockfile works (the lockfile doesn't change).
  • The library builds, and unit tests pass (16/16).
  • publint reports no errors (its earlier "no engines.node field" suggestion is resolved).
  • The packed package contains the new peerDependencies and engines values.

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.
@vercel

vercel Bot commented Oct 8, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
next-cloudinary Ready Ready Preview Oct 8, 2026 4:17pm UTC

Request Review

@PaulBoye-py PaulBoye-py changed the title Chore/raise version floors chore: raise minimum supported Next.js, React and Node.js versions Oct 8, 2026
@PaulBoye-py
PaulBoye-py removed the request for review from eportis-cloudinary October 12, 2026 20:31
@PaulBoye-py
PaulBoye-py marked this pull request as ready for review October 12, 2026 20:33
@PaulBoye-py
PaulBoye-py merged commit 2bf455c into beta Oct 12, 2026
7 checks passed
@PaulBoye-py
PaulBoye-py deleted the chore/raise-version-floors branch October 12, 2026 20:33

This branch was successfully deployed

1 active deployment
Preview — f17dfb3f Deployed Oct 8, 2026 by vercel[bot]
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