Packages

@vercel/redwood

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

Upgrading @vercel/redwood From 15.0.0 to 29.0.0

24 releases in betweennotes for 16

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

Counted from 16 of 24 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. 16.0.0 – 24.0.114 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.