releases.shpreview

`@vercel/client` agent option replaced; flags version history added

vercel@56.2.1

July 15, 2026Vercel CLIView original ↗
2 features5 enhancementsThis release2 featuresNew capabilities5 enhancementsImprovements to existing featuresAI-tallied from the release notes
From the original release noteView original ↗

Patch Changes

  • ce094f1: Show a specific error message when purchasing v0 credits without a paid v0 plan, instead of the generic unexpected-error fallback.

  • 3e0e6a8: Refactor linked project resolution to use named options.

  • 877c1ba: Allow vercel env ls to target a project explicitly without linking the current directory.

  • 81360cf: Use /v5/certs instead of legacy /v5/now/certs when listing custom certs for a domain.

  • a6af051: Add vercel flags versions <flag> and vercel flags versions diff <flag> --revision <number> to inspect feature flag version history and changes.

    Examples:

    vercel flags versions my-flag
    vercel flags versions my-flag --environment production
    vercel flags versions diff my-flag --revision 4
  • 51c7c32: vercel logs --follow now resolves a deployment automatically instead of erroring. When no deployment is specified it follows, in order: the latest deployment on the current git branch (using the provider-agnostic branch filter, which also matches deployments from unrecognized git remotes), your latest deployment, then the latest production deployment. --environment production streams the latest production deployment directly, and --environment preview restricts resolution to preview deployments.

  • 51c7c32: vercel logs now defaults to --expand output when stderr is not a TTY (agents, pipes, CI), printing every log message in full instead of truncating messages to a fixed-width table column.

  • def07fc: Migrate @vercel/client and @vercel/build-utils from node-fetch to native fetch. This removes the last url.parse() usage from the CLI bundle, which triggered a DEP0169 DeprecationWarning on Node 24 (visible in the standalone binary during vercel deploy).

    BREAKING CHANGE (@vercel/client): the agent?: http.Agent option was replaced with dispatcher?: FetchDispatcher (an undici dispatcher, e.g. undici.ProxyAgent), since native fetch does not support Node.js HTTP agents. The CLI now threads its proxy-aware dispatcher through automatically, so HTTP_PROXY/HTTPS_PROXY behavior is unchanged for CLI users.

  • 75342cb: Resolve an explicit scope before looking up a project for local builds.

  • b16a9a2: Standardize explicit project resolution across existing project-aware commands.

  • 075dc0c: Respect explicit project and scope selection when resolving project context.

  • Updated dependencies [def07fc]

    • @vercel/build-utils@13.33.1
    • @vercel/backends@0.8.24
    • @vercel/container@0.0.5
    • @vercel/elysia@0.1.101
    • @vercel/express@0.1.115
    • @vercel/fastify@0.1.104
    • @vercel/go@3.10.2
    • @vercel/h3@0.1.110
    • @vercel/hono@0.2.104
    • @vercel/hydrogen@1.4.0
    • @vercel/koa@0.1.84
    • @vercel/nestjs@0.2.105
    • @vercel/next@4.20.4
    • @vercel/node@5.8.25
    • @vercel/python@6.50.0
    • @vercel/redwood@2.5.0
    • @vercel/remix-builder@5.9.1
    • @vercel/ruby@2.5.1
    • @vercel/rust@1.4.0
    • @vercel/static-build@2.11.7

Fetched July 16, 2026