Packages

@vercel/next

31.0.2 · 20 Nov 2026Apache-2.05.8M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/next From 26.0.2 to 31.0.2

12 releases in betweennotes for 1

31.0.0, 30.0.0, 29.0.0, 28.0.0 have no release note on GitHub or in the repository's changelog, so their breaking changes are missing from the counts below. The note of 27.0.0 lists no breaking change or deprecation, which is rare for a major.
  1. 26.0.2yours
  2. 27.0.0major
  3. 1 release
  4. 28.0.0major
  5. 1 release
  6. 29.0.0major
  7. 1 release
  8. 30.0.0major
  9. 2 releases
  10. 31.0.0major
  11. 1 release
  12. 31.0.2target
  13. 19 pre
?
changes to make
0
advisories fixed
?
new
?
fixes

Counted from 1 of 12 release notes. Advisories are counted from the advisory database, in full.

The notes we hold say nothing beyond version numbers.

1 internal line (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.