Packages

@vercel/next

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

Upgrading @vercel/next From 23.0.1 to 31.0.2

19 releases in betweennotes for 8

Other targets from 23.0.1Newest 23.x23.0.3
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 notes of 27.0.0, 26.0.0, 25.0.0, 24.0.0 list no breaking change or deprecation, which is rare for a major.
  1. 23.0.1yours
  2. 2 releases
  3. 24.0.0major
  4. 25.0.0major
  5. 26.0.0major
  6. 2 releases
  7. 27.0.0major
  8. 1 release
  9. 28.0.0major
  10. 1 release
  11. 29.0.0major
  12. 1 release
  13. 30.0.0major
  14. 2 releases
  15. 31.0.0major
  16. 1 release
  17. 31.0.2target
  18. 19 pre
?
changes to make
0
advisories fixed
?
new
1+
fix

Counted from 8 of 19 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. 23.0.2 – 26.0.16 releases, nothing new or fixed in the notes

8 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.