Packages

@vercel/client

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

Upgrading @vercel/client From 18.4.4 to 18.12.4

31 releases in betweennotes for 23

Reading releases, release notes and advisories…

  1. 18.4.4yours
  2. 9 releases
  3. 18.8.0breaking
  4. 12 releases
  5. 18.10.0breaking
  6. 7 releases
  7. 18.12.4target
  8. 16 pre
3+
changes to make
0
advisories fixed
3+
new
5+
fixes

Counted from 23 of 31 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
  • Deprecated18.9.0

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.

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