Packages

@vercel/next

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

Upgrading @vercel/next From 26.0.0 to 31.0.2

14 releases in betweennotes for 3

Other targets from 26.0.0Newest 26.x26.0.2
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.0yours
  2. 2 releases
  3. 27.0.0major
  4. 1 release
  5. 28.0.0major
  6. 1 release
  7. 29.0.0major
  8. 1 release
  9. 30.0.0major
  10. 2 releases
  11. 31.0.0major
  12. 1 release
  13. 31.0.2target
  14. 19 pre
?
changes to make
0
advisories fixed
?
new
1+
fix

Counted from 3 of 14 release notes. Advisories are counted from the advisory database, in full.

Release by release

  1. 27.0.0 – 31.0.212 releases, nothing new or fixed; 11 without a note

  2. 26.0.2

    23 Oct 20261 fix
    • Fixed

      Report the runtime preset for services without a framework.

  3. 26.0.1nothing new or fixed in the note

3 internal lines (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.