Packages

@vercel/redwood

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

Upgrading @vercel/redwood From 16.0.0 to 29.0.0

23 releases in betweennotes for 15

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

Counted from 15 of 23 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. 17.0.0 – 24.0.113 releases, nothing new or fixed in the notes

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