Packages

@vercel/client

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

Upgrading @vercel/client From 17.2.11 to 17.6.5

93 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 17.2.11Latest18.12.4
  1. 17.2.11yours
  2. 26 releases
  3. 17.2.38breaking
  4. 65 releases
  5. 17.6.5target

Before you upgrade

Tick each one off as you go
  • Breaking17.2.38

Release by release

  1. 17.6.5nothing new or fixed in the note

  2. 17.6.4

    9 Jul 20261 fix
    • Fixed

      Finish CLI deployments from alias-assigned build stream events while retaining deployment polling as a fallback.

  3. 17.6.3nothing new or fixed in the note

  4. 17.6.2

    25 Jun 20261 fix
    • Fixed

      Handle deployments containing very large files without crashing. Files larger than Node's fs.readFile limit (~2 GiB) are now hashed and uploaded by streaming instead of being read into a single Buffer (which threw ERR_FS_FILE_TOO_LARGE — "File size ... is greater than 2 GiB"), and the CLI upload progress no longer assumes every file is held in memory. When a file still exceeds the server's per-request upload limit (HTTP 413), the CLI now suggests --archive=tgz, which uploads the deployment in smaller chunks.

  5. 17.6.1

    24 Jun 20261 new
    • New

      Add vercel deploy --dry to inspect the detected framework preset and local deployment file set without uploading or creating a deployment, with complete JSON output for non-TTY consumers.

  6. 17.6.0

    24 Jun 20261 new
    • New

      Add services as the canonical multi-service project configuration and keep experimentalServicesV2 as a deprecated backwards-compatible alias.

  7. 17.5.9 – 17.5.1810 releases, nothing new or fixed in the notes

  8. 17.5.8

    3 Jun 20261 new · 1 fix
    • New

      Add experimentalServicesV2 field to vercel.json implementing the new schema for services.

    • Fixed

      Remove the services field from vercel.json and the VERCEL_USE_SERVICES gate.

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