Packages

@vercel/next

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

Upgrading @vercel/next From 17.0.0 to 31.0.2

28 releases in betweennotes for 17

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

Counted from 17 of 28 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.

  5. 18.0.0 – 20.0.03 releases, nothing new or fixed in the notes

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