Packages

@vercel/next

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

Upgrading @vercel/next From 20.0.0 to 31.0.2

25 releases in betweennotes for 14

Other targets from 20.0.0Newest 20.x20.0.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 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.0yours
  2. 1 release
  3. 21.0.0major
  4. 22.0.0major
  5. 1 release
  6. 23.0.0major
  7. 3 releases
  8. 24.0.0major
  9. 25.0.0major
  10. 26.0.0major
  11. 2 releases
  12. 27.0.0major
  13. 1 release
  14. 28.0.0major
  15. 1 release
  16. 29.0.0major
  17. 1 release
  18. 30.0.0major
  19. 2 releases
  20. 31.0.0major
  21. 1 release
  22. 31.0.2target
  23. 19 pre
?
changes to make
0
advisories fixed
?
new
2+
fixes

Counted from 14 of 25 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

  4. 20.0.1

    6 Oct 20261 fix
    • Fixed

      Reject immutable static assets in Next.js static export builds when not using the adapter.

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.