Packages

@vercel/client

18.12.4 · 18 Nov 2026Apache-2.0119.5k / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/client From 1.0.3 to 18.12.4

392 releases in betweennotes for 239

Reading releases, release notes and advisories…

13.0.0, 12.0.0, 11.0.0, 10.0.0, 9.0.0, 8.0.0 have no release note on GitHub or in the repository's changelog, so their breaking changes are missing from the counts below.
  1. 1.0.3yours
  2. 8.0.0major
  3. 4 releases
  4. 9.0.0major
  5. 8 releases
  6. 10.0.0major
  7. 8 releases
  8. 11.0.0major
  9. 4 releases
  10. 12.0.0major
  11. 77 releases
  12. 13.0.0major
  13. 69 releases
  14. 14.0.0major
  15. 1 release
  16. 15.0.0major
  17. 32 releases
  18. 16.0.0major
  19. 1 release
  20. 17.0.0major
  21. 114 releases
  22. 18.0.0major
  23. 27 releases
  24. 18.4.0security
  25. 34 releases
  26. 18.12.4target
  27. 16 pre
10+
changes to make
0
advisories fixed
27+
new
32+
fixes

Counted from 239 of 392 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking18.10.0
  • Breaking18.8.0
  • Breaking18.0.0
  • Breaking17.2.38
  • Breaking17.0.0
  • Breaking16.0.0
  • Breaking15.0.0
  • Breaking14.0.0
  • Breaking14.0.0
  • Deprecated18.9.0

Security

Release by release

  1. 18.10.1 – 18.12.48 releases, no release note

  2. 18.10.0

    Migration needed27 Oct 2026
    • Breaking

      Remove the deprecated array format for schedules. schedules in vercel.json, in Build Output config.json, and from getDevManifest must be an object keyed by schedule name. @vercel/config no longer exports Schedule (use ScheduleDefinition), and @vercel/client no longer exports VercelConfigSchedule.

  3. 18.9.1 – 18.9.33 releases, nothing new or fixed in the notes

  4. 18.9.0

    Deprecation20 Oct 2026
    • Deprecated

      schedules in vercel.json can now be an object keyed by schedule name, like "schedules": { "nightly": { "schedule": "0 0 * * *", "path": "/api/cron" } }. vercel build writes schedules to Build Output config.json in the format it was given, and builders can return it from getDevManifest. The array of named schedules still works but is deprecated, and vercel build and vercel dev warn when it's used.

  5. 18.8.6 – 18.8.83 releases, nothing new or fixed in the notes

  6. 18.8.5

    15 Oct 20261 fix
    • Fixed

      Prevent deployment archives from including ignored files through directory entries.

  7. 18.8.2 – 18.8.43 releases, nothing new or fixed in the notes

  8. 18.8.1

    8 Oct 20261 fix
    • Fixed

      Retry transient upload and deployment status failures, improve network diagnostics, and clarify errors when a deployment outcome cannot be confirmed.

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