Packages

@vercel/redwood

29.0.0 · 18 Nov 2026Apache-2.05.2M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/redwood From 3.0.0 to 29.0.0

44 releases in betweennotes for 36

29.0.0, 28.0.0, 27.0.0, 26.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 25.0.0, 24.0.0, 23.0.0, 22.0.0, 21.0.0, 20.0.0, 19.0.0, 18.0.0, 17.0.0, 16.0.0, 15.0.0, 14.0.0, 13.0.0, 12.0.0, 11.0.0, 10.0.0, 9.0.0, 8.0.0, 7.0.0, 4.0.0 list no breaking change or deprecation, which is rare for a major.
  1. 3.0.0yours
  2. 4.0.0major
  3. 3 releases
  4. 7.0.0major
  5. 8.0.0major
  6. 9.0.0major
  7. 3 releases
  8. 10.0.0major
  9. 2 releases
  10. 11.0.0major
  11. 12.0.0major
  12. 13.0.0major
  13. 2 releases
  14. 14.0.0major
  15. 15.0.0major
  16. 16.0.0major
  17. 17.0.0major
  18. 18.0.0major
  19. 19.0.0major
  20. 20.0.0major
  21. 1 release
  22. 21.0.0major
  23. 3 releases
  24. 22.0.0major
  25. 23.0.0major
  26. 24.0.0major
  27. 2 releases
  28. 25.0.0major
  29. 1 release
  30. 26.0.0major
  31. 1 release
  32. 27.0.0major
  33. 28.0.0major
  34. 2 releases
  35. 29.0.0target
  36. 15 pre
?
changes to make
0
advisories fixed
?
new
2+
fixes

Counted from 36 of 44 release notes. Advisories are counted from the advisory database, in full.

Release by release

  1. 25.0.0 – 29.0.09 releases, nothing new or fixed; 8 without a note

  2. 24.0.2

    23 Oct 20261 fix
    • Fixed

      Report the runtime preset for services without a framework.

  3. 5.0.3 – 24.0.132 releases, nothing new or fixed in the notes

  4. 5.0.1

    26 Aug 20261 fix
  5. 4.0.0nothing new or fixed in the note

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