Packages

@vercel/next

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

Upgrading @vercel/next From 20.0.1 to 31.0.2

24 releases in betweennotes for 13

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

Counted from 13 of 24 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. 21.0.0 – 26.0.111 releases, nothing new or fixed in the notes

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