Packages

@vercel/redwood

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

Upgrading @vercel/redwood From 6.0.1 to 29.0.0

40 releases in betweennotes for 32

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

Counted from 32 of 40 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. 7.0.0 – 24.0.130 releases, nothing new or fixed in the notes

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