Skip to content

chore(deps): update dependency vercel to v54.20.0#1007

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vercel-54.x-lockfile
Open

chore(deps): update dependency vercel to v54.20.0#1007
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vercel-54.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Jun 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
vercel (source) 54.12.2 → 54.20.0 age confidence

Release Notes

vercel/vercel (vercel)

v54.20.0

Compare Source

Minor Changes
  • b9e4f06: Add a vercel agent-runs command for Agent Runs observability: list lists Agent Runs for a project, inspect <runId> shows run metadata, events, usage, and subagents, trace <runId> shows the full trace (turns, messages, reasoning, and tool calls), and projects lists projects in the team with Agent Runs activity. All subcommands support --json for machine-readable output.

v54.19.0

Compare Source

Minor Changes
  • 2c87793: Add vercel vcr commands to manage Vercel Container Registry repositories and images.
Patch Changes
  • 84c01ff: Add install as an alias for vercel integration add.
  • 08d234f: Merge routes from generated Build Output config with builder routes when nesting Services V2 output, so framework routes and generated service or custom routes are all preserved.
  • 6e004b1: Accept all marketplace integration legal documents (addendum, privacy policy, terms of service) with a single confirmation instead of one prompt each. The links are now listed together, each on its own line, before asking.

v54.18.7

Compare Source

Patch Changes

  • 4d9394b: Bridge WebSocket close to response close

  • c4667d3: Fix vc build run from a monorepo subdirectory (gated behind VERCEL_RESOLVE_ROOT_DIRECTORY=1).

    When a project is linked in place (apps/api/.vercel/project.json) and vc build is run from that directory, the build previously treated the linked subdirectory as the repository root. Because the project's dependencies are typically hoisted to the monorepo root above it, this broke builds in several ways that share one root cause:

    • A rootDirectory setting that restates the link's own location (e.g. apps/api for a link at apps/api) double-appended into apps/api/apps/api, failing with ENOENT … /apps/api/apps/api/.next/package.json.
    • With --standalone, the package-manager symlink that makes a dependency resolvable (apps/api/node_modules/hono → ../../node_modules/.pnpm/.../hono) was skipped because its target pointed outside the subdirectory, so the deployed function failed at runtime with Cannot find module 'hono' even though the dependency's files were packaged.
    • Builders traced from the wrong root, so Next.js set an incorrect outputFileTracingRoot/turbopack.root (Turbopack errors; Webpack .nft.json omits hoisted dependencies).

    With the flag enabled, a per-directory link is resolved like a repository-level link: the repository root is detected (workspace markers, then git) and the project is expressed as its path relative to that root, so the build is anchored correctly regardless of which directory the command is run from. The rootDirectory setting is interpreted relative to the link's location and honored when it points at a folder that exists; otherwise (e.g. the redundant apps/api/apps/api case) it is ignored in favor of the link's own location and a warning is emitted. Standalone builds additionally preserve the package-manager symlinks (rather than skipping them) so dependencies resolve at runtime. Behavior is unchanged when the flag is not set.

  • Updated dependencies [69892ba]

v54.18.6

Compare Source

Patch Changes

v54.18.5

Compare Source

Patch Changes
  • 0eea3d6: Expose cacheReason in vc logs output, alongside the existing cache status, so users can see why a request was a cache MISS/BYPASS/STALE.

v54.18.4

Compare Source

Patch Changes
  • 16cf8f6: Surface the builds rate-limit upgrade hint on vercel deploy. The hint previously never printed (the error was dropped before conversion) and pointed at the CLI self-updater; it now renders the backend's plan-appropriate call to action (ctaLabel/ctaUrl, or legacy action/link) from the error, falling back to a plan-agnostic nudge.
  • 56875d2: Remove the non-functional vercel buy v0 subcommand; use vercel buy credits v0 to purchase v0 credits.
  • 6c5aa14: Support lazily generated Build Output services configs during vc build.

v54.18.3

Compare Source

Patch Changes

  • 262e935: Fixed vercel dev for the container framework when used as a top-level build (outside of services).

    • The dev server now maps the container preset's <detect> sentinel to a discovered Dockerfile (Dockerfile.vercel, Containerfile.vercel, Dockerfile, or Containerfile), so the build is recognized instead of warning that it "did not match any source files".
    • The @vercel/container build() path no longer throws `vercel dev` cannot build container images from a Dockerfile during dev. Containers are always built from a Dockerfile/Containerfile (there is no prebuilt-image input); in dev the image is built and run locally by startDevServer, so build() returns a stable local tag without pushing to a registry.
    • The dev server no longer treats a container build output (an OCI image reference, runtime: "container") as a zip-based function. It previously failed with output.createZip is not a function while trying to spin the image up under fun; container outputs are now skipped there and served by the builder's startDevServer instead.
    • The dev path (startDevServer) now discovers the Dockerfile.vercel / Containerfile.vercel opt-in markers when the container entrypoint is the <detect> sentinel, matching the build path. Previously it only looked for a bare Dockerfile, so a project using a .vercel marker failed with "Container service must specify an entrypoint…" even though deploys worked. The discovery helper is now shared between the build and dev paths.
    • vercel dev now fails fast with a clear message when the Docker daemon isn't running ("Could not connect to the Docker daemon. Start Docker…") instead of a cryptic Container "undefined" exited (code 125) before becoming ready.. Container start failures also now name the actual container and include the underlying Docker error output.
    • The container dev server is now reused across requests. Previously the image was rebuilt and a fresh container started on every HTTP request (the result was missing the persistent flag); now a live container is kept and reused for the same service, matching how other persistent builders behave.

  • 9e3f9cd: [services] service name validation

  • 9e3f9cd: Align services and experimentalServicesV2 service-name validation with the platform schema.

  • Updated dependencies [262e935]

  • Updated dependencies [e05ed3c]

v54.18.2

Compare Source

Patch Changes

v54.18.1

Compare Source

Patch Changes

v54.18.0

Compare Source

Minor Changes
  • 4f8b5b1: - Migrate service auto-detection to V2 format.
    • Layout auto-detect now resolves via the V2 resolver and generates top-level service-targeted rewrites and per-service path transform routes.
    • CLI build and dev server merge auto-detected rewrites into the route table.
Patch Changes
  • 50276e7: Show the flags command in the top-level CLI help output.
  • 6881d74: Use Node.js native fetch for the CLI API client, removing legacy URL parser deprecation warnings from standalone binaries while preserving proxy routing and local middleware behavior.
  • 6514009: Fix CLI update notification showing a stale or incorrect version number. The update prompt now performs a fresh registry lookup before displaying the target version, and the upgrade success message reports the actually installed version instead of the prompted version.
  • 69f15ee: vercel flags ls now uses the v2 flag list endpoint and supports filtering by --tag, --created-by, and --maintainer-id, plus cursor pagination via --limit (page size) and --next (resume cursor).
  • c1641e4: Update integration error and warning hints to suggest the canonical vercel integration resource form instead of the legacy vercel integration-resource alias
  • ee389a1: Support WebSockets for WSGI apps (e.g. Flask via flask-sock). The runtime now
    exposes the raw connection socket in the WSGI environ as werkzeug.socket /
    gunicorn.socket for WebSocket upgrade requests, and ends the request lifecycle
    once the 101 handshake is written so the platform can begin bidirectional
    streaming — matching the ASGI websocket.accept behavior.
  • 62a884e: Simplify isolated services and experimentalServicesV2 runtime outputs by emitting their function at index instead of _svc/<service-name>/index.
  • Updated dependencies [66be3e0]
  • Updated dependencies [62a884e]

v54.17.3

Compare Source

Patch Changes
  • f76b357: Improve vercel domains add: skip project/deployment configuration guidance when no project is provided, return a specific error explaining only apex domains can be added without a project, treat a domain already assigned to the requested project as a success instead of failing with an "assigned to another project" error, and point users to vercel domains verify <domain> for DNS configuration instead of printing hardcoded DNS records.
  • Updated dependencies [4b90a10]
  • Updated dependencies [34b2c4c]

v54.17.2

Compare Source

Patch Changes

  • 6eb572e: Add vercel edge-config backups for listing, inspecting, and restoring Edge Config backups.

    Examples:

    • vercel edge-config backups my-store
    • vercel edge-config backups my-store --backup-version <backup-version-id> --format json
    • vercel edge-config backups my-store --restore <backup-version-id> --yes

  • 7cecf55: Make hand-written service-targeted route/rewrite destination config less repetitive and verbose by making the type discriminator optional.

     {
   "rewrites": [{
-    "type": "service",
     "service": "my_backend",
     "path": "/api/$1"
   }]
 }

    The explicit { "type": "service", "service": NAME } format continues to
    validate. Normalized route output continues to include "type": "service", so
    machine-facing config remains canonical.

  • 5d37c78: 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.

v54.17.1

Compare Source

Patch Changes
  • 2f85145: Expose ordering controls, returned ordering metadata, and a --prod shortcut for metrics queries, and update Speed Insights metric examples.
  • aeb8bf1: vc build now writes experimentalServicesV2 services into the Build Output API config.json services array (previously only experimentalServices were included), so V2 services are recorded on the deployment.
  • Updated dependencies [d538795]

v54.17.0

Compare Source

Minor Changes
  • 222d43b: Fix websocket upgrade events for services V2.
Patch Changes

v54.16.0

Compare Source

Minor Changes
  • 9fb2976: Add services as the canonical multi-service project configuration and keep experimentalServicesV2 as a deprecated backwards-compatible alias.
  • 260b0be: Support the VQS idempotency key header in the local development server.
Patch Changes

  • 6a43bf2: Adding 2 additional headers to Vercel API calls

  • 186014d: Fix vc dev erroring with "Project framework is set to 'services', but no
    services are declared" for experimentalServicesV2 (services) projects. When
    the dev server already has resolved services, it now skips zero-config builder
    detection and lets the services orchestrator build and run them. Previously
    detectBuilders ran with the remote framework: "services" setting but no
    service config threaded in, which failed even though detection had succeeded.

  • 186014d: Add an experimental container service runtime. A service with
    runtime: "container" either builds its Dockerfile/Containerfile and pushes
    the resulting OCI image to the Vercel Container Registry (VCR), or passes a
    prebuilt image reference through as build output.

    • @vercel/container (new builder): authenticates to VCR with the project's
      VERCEL_OIDC_TOKEN, ensures the repository exists, builds and pushes the
      image, and emits a digest-pinned reference in handler (container functions
      are type: "Lambda" with runtime: "container"; the platform surfaces
      handler as the image downstream). Uses docker on developer machines and
      buildah (daemonless) in the Vercel build container behind a shared
      ContainerEngine interface. Supports vc dev via startDevServer (local
      build/run, env parity, log forwarding) and prepareCache for buildah layer
      reuse between builds. Build flow is instrumented with tracing spans
      (non-secret diagnostics) and debug logging gated on BUILDER_DEBUG.
    • @vercel/build-utils: add the ContainerImage build-output type.
    • @vercel/fs-detectors: resolve container services from vercel.json
      (the services config and its deprecated experimentalServices /
      experimentalServicesV2 aliases). A Dockerfile, Containerfile, or
      *.dockerfile entrypoint triggers a build; any other entrypoint is treated as
      a prebuilt OCI image reference.
    • vercel: wire container output into vercel build result writing and
      config validation.

    Buildah specifics in the build container: host networking for RUN steps,
    native overlay storage on the XFS /vercel volume (deferring to the image's
    storage.conf), zstd push compression, and registry credentials read from the
    provisioned auth file when present. Several knobs are available for debugging:
    VERCEL_CONTAINER_ENGINE, VERCEL_VCR_STRICT_STORAGE,
    VERCEL_VCR_DISABLE_LAYER_CACHE, and VERCEL_VCR_FORCE_LOGIN.

  • 007af8f: Deduplicate the team billing settings URL into a shared getTeamBillingUrl helper.

  • edb7256: [vc dev] Apply route transforms under vercel dev.

  • 1c5d3b3: Fixed scope resolution for Northstar accounts whose username collides with the slug of their default team.

    • Commands now scope API requests to the Northstar default team on every invocation, not just at login. Previously the default team was resolved for display (vc whoami showing "Active team: my-user") while requests were sent with no teamId, silently scoping to the resource-less personal account. This caused commands like vc projects ls to report "No projects found" even though the team has projects.
    • --scope <name> now resolves against the user's teams before falling back to personal-account handling. A team whose slug matches the user's username (e.g. a Northstar default team) can now be selected by name instead of being rejected with "You cannot set your Personal Account as the scope."

  • ded2d92: Refresh VERCEL_OIDC_TOKEN after vercel link without overwriting other
    variables or formatting in an existing .env.local file.

  • Updated dependencies [fdb6121]

  • Updated dependencies [9fb2976]

  • Updated dependencies [186014d]

  • Updated dependencies [186014d]

  • Updated dependencies [186014d]

  • Updated dependencies [e6759d0]

  • Updated dependencies [68ed45c]

  • Updated dependencies [cb0988f]

v54.15.1

Compare Source

Patch Changes

v54.15.0

Compare Source

Minor Changes

  • 8dec9ea: Add deploy-manifest as an extension of project manifest.

  • d99dbf8: Add vercel domains verify <domain> for DNS misconfiguration feedback. The command checks the domain's DNS configuration, reports dashboard-aligned configuration and project-verification states, triggers a verification re-check when needed, and lists actionable fixes: recommended A/CNAME records, Vercel nameservers, conflicting records, DNSSEC guidance, and the TXT ownership challenge. Domains eligible for automatic configuration also receive a Domain Connect URL, with manual DNS guidance as a fallback. Supports --project, --strict, and --format json; non-interactive runs emit structured status, simultaneous issue details, automatic-configuration metadata, and shell-safe, context-preserving next commands. Human and structured output share one diagnosis so status, remediation, and exit behavior stay consistent. The command exits non-zero when action is required so scripts and agents can gate on it.

  • a5245fd: Add vercel flags segments commands for listing, inspecting, creating, updating, and deleting feature flag segments.

    Examples:

    vercel flags segments ls
vercel flags segments inspect beta-users --json
vercel flags segments create beta-users --label "Beta users" --add include:user.id=user_123 --add include:user.id=user_456
vercel flags segments create enterprise-users --label "Enterprise users" --add rule:user.plan:eq:enterprise
vercel flags segments update beta-users --add include:user.id=user_789 --remove include:user.id=user_123
vercel flags segments update enterprise-users --add rule:user.email:ends-with:@&#8203;company.com --remove rule:user.plan:eq:pro
vercel flags segments update enterprise-users --data '{"rules":[],"include":{"user":{"email":[{"value":"me@company.com"}]}},"exclude":{}}'
vercel flags segments rm beta-users --yes
Patch Changes

v54.14.5

Compare Source

Patch Changes
  • d1e1d69: Stop prompting to install the Vercel plugin after login and link commands.
  • 7aa52be: Show bounded progress while upgrading native and package-installed CLIs, and
    report when no newer version is available without running the installer.
  • e2043e6: Build standalone Vercel CLI binaries with Node.js 24.14.1.
  • Updated dependencies [94671a4]
  • Updated dependencies [d4547af]
  • Updated dependencies [bc6f22f]
  • Updated dependencies [f530cd5]

v54.14.2

Compare Source

Patch Changes
  • 8e56ad5: Add experimental shim to enable Next.js WebSocket upgrade support in vc dev.
  • 07d3fe2: [cli] Add traces create as an alias for curl --trace

v54.14.1

Compare Source

Patch Changes
  • 3d6f057: [cli] Make vercel blob store commands work non-interactively for agents
  • 28dda45: Update Claude Code Vercel plugin prompts and remember accepted plugin updates for future automatic updates.
  • d55310f: Add CLI UX guidance and improve CLI output consistency.
  • b341a19: Improve CLI version output: the native binary now prints Vercel CLI <version> without the Node.js suffix, and vercel upgrade reports the version it upgraded to and says "No upgrade available" when already on the latest version.
  • 7f5f0f2: Fix telemetry flushing when running the CLI as a native binary.
  • 7866d3d: Allow vercel buy addon customEnvironment <quantity> by adding customEnvironment to the CLI add-on allowlist and help examples.
  • b7fbaec: Improve vc metrics: source groupable dimensions from the metric schema instead of a hardcoded list, preserve the requested time bounds so the query endpoint owns bucket rounding, and add an optional --bucket-timezone flag for calendar bucket alignment (it only affects bucket boundaries, not the --since/--until range or output timestamps).
  • e9aa6f5: Remove hidden --functions-beta / --no-functions-beta deploy flags and the size-limit hint messaging
  • fd26487: Remove deprecated public from deployment test fixtures and helpers, and stop the CLI from sending the removed public field on deploy (including the --public flag).
  • 5ed337e: Allow vercel metrics to combine repeated --filter/-f values with OData and.
  • aeea9f2: Render the ▲ gutter once per deploy summary: on the Aliased row, falling back to the Production row when no Aliased row will print (--no-wait, --skip-domain)
  • Updated dependencies [e9aa6f5]

v54.14.0

Compare Source

Minor Changes
  • 210748e: [cli] Add vercel ai-gateway rules add/list/edit/remove commands
Patch Changes

v54.13.0

Compare Source

Minor Changes
  • 128ad88: Add --category / -c filter to vercel integration discover and a new vercel integration categories subcommand. The filter scopes marketplace integrations to a single category (e.g. storage, ai, monitoring) — filtering happens server-side. The new categories subcommand lists the valid slugs (Slug | Title table or --json for scripts/agents).
Patch Changes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 14, 2026 •
edited
Loading

Copy link
Copy Markdown

Deploying website with  Cloudflare Pages  Cloudflare Pages

Latest commit: 7f1e4fc
Status: ✅  Deploy successful!
Preview URL: https://d17ccbdf.website-mhmf.pages.dev
Branch Preview URL: https://renovate-vercel-54-x-lockfil.website-mhmf.pages.dev

View logs

@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.13.0 chore(deps): update dependency vercel to v54.14.0 Jun 14, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from a1d1bfa to f504aed Compare June 17, 2026 18:43
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.14.0 chore(deps): update dependency vercel to v54.14.1 Jun 17, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.14.1 chore(deps): update dependency vercel to v54.14.2 Jun 18, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from f504aed to 28d5214 Compare June 20, 2026 21:47
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.14.2 chore(deps): update dependency vercel to v54.14.5 Jun 20, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from 28d5214 to 9e81c30 Compare June 23, 2026 05:48
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.14.5 chore(deps): update dependency vercel to v54.15.0 Jun 23, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.15.0 chore(deps): update dependency vercel to v54.15.1 Jun 23, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from 9e81c30 to 96ee21c Compare June 24, 2026 17:42
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.15.1 chore(deps): update dependency vercel to v54.16.0 Jun 24, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.16.0 chore(deps): update dependency vercel to v54.17.0 Jun 25, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.17.0 chore(deps): update dependency vercel to v54.17.1 Jun 25, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from 96ee21c to 0b11428 Compare June 25, 2026 18:31
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.17.1 chore(deps): update dependency vercel to v54.17.2 Jun 25, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.17.2 chore(deps): update dependency vercel to v54.17.3 Jun 25, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from 0b11428 to cbff307 Compare June 26, 2026 22:57
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.17.3 chore(deps): update dependency vercel to v54.18.0 Jun 26, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from cbff307 to 3f91953 Compare June 28, 2026 01:56
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.18.0 chore(deps): update dependency vercel to v54.18.1 Jun 28, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from 3f91953 to 3e96bc2 Compare June 28, 2026 23:50
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.18.1 chore(deps): update dependency vercel to v54.18.2 Jun 28, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.18.2 chore(deps): update dependency vercel to v54.18.4 Jun 29, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from 3e96bc2 to 0c8733d Compare June 30, 2026 03:52
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.18.4 chore(deps): update dependency vercel to v54.18.5 Jun 30, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from 0c8733d to d4cda26 Compare June 30, 2026 16:15
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.18.5 chore(deps): update dependency vercel to v54.18.6 Jun 30, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from d4cda26 to a5ac11c Compare July 1, 2026 23:56
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.18.6 chore(deps): update dependency vercel to v54.18.7 Jul 1, 2026
@renovate renovate Bot force-pushed the renovate/vercel-54.x-lockfile branch from a5ac11c to 7f1e4fc Compare July 2, 2026 21:16
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.18.7 chore(deps): update dependency vercel to v54.19.0 Jul 2, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vercel to v54.19.0 chore(deps): update dependency vercel to v54.20.0 Jul 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants