Packages

@vercel/next

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

Upgrading @vercel/next From 22.0.1 to 31.0.2

21 releases in betweennotes for 10

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

Counted from 10 of 21 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.0 – 26.0.18 releases, nothing new or fixed in the notes

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