Skip to content

Update dependency vercel to v56#33

Open
renovate[bot] wants to merge 1 commit into
v2from
renovate/vercel-56.x
Open

Update dependency vercel to v56#33
renovate[bot] wants to merge 1 commit into
v2from
renovate/vercel-56.x

Conversation

@renovate

@renovate renovate Bot commented Jul 13, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vercel (source) ^36.0.0 → ^56.0.0 age confidence

Release Notes

vercel/vercel (vercel)

v56.2.0

Compare Source

Minor Changes
  • 997d319: vercel env add now accepts a comma-separated list of environments to create a single Environment Variable entry spanning multiple targets, e.g. vercel env add API_URL production,preview,development. Invalid environment names fail locally with a clear error (invalid_environment in non-interactive mode), custom Environment slugs are resolved to ids, and a Git branch is rejected unless Preview is the only target. Non-interactive missing_environment, missing_requirements, and sensitivity-conflict payloads now suggest the multi-target command form.
Patch Changes

  • e6b11f0: Add finer-grained vc.doBuild spans (vc.readConfigInputs, vc.prepareFlagsDefinitions, vc.getFiles, vc.populateFilesMap, and vc.setMonorepoDefaultSettings) so build-container traces can attribute previously unaccounted CLI orchestration time.

  • 383c0a0: Fix native-trampoline test hardcoding 55.0.0 that broke after version bump to 56.1.0.

    The test now reads the version from packages/cli/package.json and strips
    NODE_PATH/VITEST env vars so require.resolve inside the temp install does
    not leak the repo's pnpm store. Also fixes VERCEL_VC_NATIVE leak on
    ENOENT/EACCES fallback (JS fallback was mislabeled as "(native)") and
    updates the stale Part-1 comment in src/vc.js.

  • 351a9b6: Exclude vercel.ts config file variants from static file serving

v56.1.0

Compare Source

Minor Changes
  • fac79dc: Make the CLI bin native-aware: resolve and spawn a @vercel/vc-native-*
    binary when present, otherwise no-op into the existing JS CLI. Part 1 of 2;
    no optionalDependencies are wired yet, so this release is a no-op that
    confirms the JS path is unaffected. Part 2 wires the release flow to
    publish natives before vercel.
Patch Changes
  • e01c1d2: Harden filesystem trust boundaries: vercel init no longer materializes symlink or hardlink entries from downloaded example archives (blocking tar link-following path traversal, CVE-2024-12905 / CVE-2025-48387, and upgrading tar-fs to 1.16.5), the deploy root-directory check now normalizes paths before the containment test so a sibling directory sharing the project's path prefix can no longer be selected, and ai-gateway coding-agents setup now flags in its plan when a target config path is a symlink so the approval prompt reflects the file the write actually lands on.

v56.0.0

Compare Source

Major Changes
  • 4998ec8: vercel routes export now uses --output (-o) instead of --format to select the output file format (json or ts, dotted forms like .ts also accepted). This frees --format to align with the standard output-format convention used by other commands. Update any scripts from routes export --format ts to routes export --output ts.
Minor Changes
  • 5ae15fa: Add vercel ai-gateway coding-agents setup to connect Claude Code to the AI Gateway from an existing API key (--key): it sets the gateway base URL and authentication in ~/.claude/settings.json (honoring CLAUDE_CONFIG_DIR), never pins a default model, is idempotent, masks the key in output, skips unparseable configs instead of clobbering them, edits existing config files in place so your own keys and formatting are untouched, and emits a structured JSON result in non-interactive mode.
  • 24c2b3c: Automatically install a marketplace product's declared agent skills after vercel integration add provisions it, replacing the interactive confirmation prompt. The transcript ends with an install summary linking to the product's marketplace page, and failed installs fall back to printing the manual npx skills add command.
  • 607f0ef: Add service information to deploy-manifest.
  • 8642a47: Remove the vercel oauth-apps sub-command, reverting the OAuth / connected apps parity scope.
  • 57e2091: vercel env pull now keeps variables that only exist in the local env file instead of deleting them. Kept variables are listed in the command output. CLI-managed variables (VERCEL_OIDC_TOKEN and analytics IDs) are still removed when they no longer exist upstream.
Patch Changes

  • 2a403e2: Add Codex support to vercel ai-gateway coding-agents setup. It writes a vercel model provider to ~/.codex/config.toml (OpenAI-compatible base URL, responses wire API) without pinning a default model, and exports the gateway API key via your shell rc (honoring CODEX_HOME and fish/ZDOTDIR). Merging into an existing config.toml edits assignments in place, preserving your comments and formatting.

  • 683f013: ai-gateway coding-agents setup can now provision a key for you: run it without --key and it creates an AI Gateway API key (prompting for the owning team and a name, or using --name/--scope and the current scope with --yes), then writes that key into the agent configs.

    Re-running when everything is already set up is no longer a dead end: it prompts to rotate the key or switch team, and --reconfigure does the same non-interactively (useful for a rotated or expired key, or a different org). A plain re-run stays a no-op.

  • e64b222: ai-gateway coding-agents setup now detects the Codex desktop app and asks for consent before configuring Codex, since the desktop app cannot use custom model providers and stops working when one is set (the Codex CLI keeps working). Non-interactive and --yes runs configure Codex only when it is explicitly requested with --agent/--all; JSON output gains a warnings array and a requires_consent skip reason, and a run refused for lack of consent exits 1 with a self-contained requires_consent error payload (structured warnings, skip entries, and a runnable next[] command). A declined agent's configuration is left untouched.

  • 7190684: ai-gateway coding-agents setup now configures only the agents detected on the machine when run non-interactively without --agent/--all, exits with code 1 (without creating an API key) when no agent configuration can be written, and on Windows reports the environment variable to set instead of writing a shell file that is never loaded (unless --shell-rc is passed explicitly). Non-interactive re-runs with --key on an already-configured macOS Keychain setup now refresh the stored key instead of silently keeping the old one.

  • 097395b: ai-gateway coding-agents setup can now put limits on a key it creates: a spend cap (--budget with --refresh-period / --include-byok) and an expiry (--expiration 7d|30d|60d|90d|1y|none). Interactively it asks whether to set each. The limits are sent only when creating a key; reusing one with --key is unaffected.

  • fcdf5cd: Store the coding-agents setup API key in the macOS login Keychain instead of writing it into plaintext config files. When available it's used automatically: env-based agents resolve the key from the shell at runtime (a managed shell-rc block runs security find-generic-password), so the secret never lands in a config file. Pass --no-keychain, or run off macOS, to embed the key directly; it also falls back to embedding if the Keychain write fails.

  • c66bae3: Add OpenCode support to vercel ai-gateway coding-agents setup. It supplies the gateway API key to OpenCode's native vercel provider in ~/.config/opencode/opencode.json (honoring XDG_CONFIG_HOME) without pinning a default model. With the macOS Keychain in use, the key is kept out of the config and resolved from AI_GATEWAY_API_KEY (exported from the shell rc) at runtime instead.

  • 2ffbf59: Add Pi support to vercel ai-gateway coding-agents setup. It writes the gateway credential to Pi's native vercel-ai-gateway auth entry in ~/.pi/agent/auth.json (created 0600, honoring PI_CODING_AGENT_DIR) without pinning a default model.

  • bb16ec9: ai-gateway coding-agents setup now previews before it writes. --dry-run and the pre-apply summary show the planned per-file changes as a masked diff, the resolved key/quota/expiry, and the .bak backups it would create (suppressed with --no-backup), then ask for confirmation before applying. For non-standard setups, --agent-config <id>=<path> overrides an agent's config-file location and --shell-rc <path> the shell rc; interactively it offers a custom path when an agent isn't found at its default location.

  • 35fba40: Attribute marketplace agent-skill auto-installs in the skills CLI's install telemetry by passing --metadata (origin, flow, integration and product slugs) to the npx skills add invocation. Older skills versions (< 1.5.16) ignore the flag and install unchanged.

  • fd8e544: Preserve an environment's serving mode when feature flag rules are added,
    updated, moved, or removed. When the environment is serving a fixed variant,
    the CLI identifies that variant and warns that rule changes will not affect flag
    evaluation until the environment uses targeting again.

  • Updated dependencies [607f0ef]

  • Updated dependencies [7bbfd48]

  • Updated dependencies [9637ae6]

  • Updated dependencies [f11c4c4]

v55.0.0

Compare Source

Major Changes
  • 8f10c0b: Require an explicit team signal when linking without a TTY. In non-interactive
    mode or without a terminal, vercel link (and other commands that set up a
    link) no longer fall back to the globally selected team from vc switch or the
    login default, and --yes no longer guesses a team. The team now resolves only
    from --scope/--team, the scope property in vercel.json,
    VERCEL_ORG_ID, or a single available team; otherwise the command fails with
    action_required: missing_scope (JSON in non-interactive mode) before any
    project discovery runs, before a new project is created, and before the
    existing .vercel/project.json is deleted. This also removes the slow
    all-teams project search from non-interactive vercel link runs.
  • 8f10c0b: Every command that establishes a link — vercel deploy, vercel pull,
    vercel dev, vercel git connect, and vercel link itself — now uses the
    same flow: resolve the team first (explicit --scope/--team,
    vercel.json scope, VERCEL_ORG_ID, a single available team, or the
    searchable team picker), then offer project suggestions scoped to that team,
    preferring projects linked to the local Git repository (which produce a
    repo-style .vercel/repo.json link) over folder-name matches. The
    cross-team project sweep and its SSO fallback prompt are removed entirely;
    project discovery never queries teams other than the one that was resolved.
    An explicit project name (--project, --name, or vercel.json name)
    skips the suggestions and resolves directly within the team. An explicit
    team signal now also skips the team prompt in every command, not just
    vercel link.
  • 8f10c0b: --yes no longer selects a team on its own. It answers confirmations, not
    data questions: when the account has multiple teams and no explicit signal
    (--scope/--team, vercel.json scope, VERCEL_ORG_ID), an interactive
    terminal now asks Which team? once and continues auto-confirmed, instead of
    silently using the globally selected team from vc switch or the login
    default. This also removes the all-teams project sweep from vercel link --yes; matches are resolved within the chosen team, and a single Git-linked
    root-directory match still links automatically.
Minor Changes
  • 0922f27: Add vercel integration resource inspect <resource> (alias status) to show a marketplace resource's details and live status fetched fresh from the provider, rather than the cached status shown by vercel integration list. Supports --format=json.
  • 8f10c0b: vercel link now honors VERCEL_ORG_ID and VERCEL_PROJECT_ID as an
    explicit project-owner pair: when both are set, the command resolves and
    confirms exactly that pair without prompting and without --yes, and leaves
    local link files untouched. An unresolvable pair errors instead of falling
    back to prompts. The new-project Name? prompt also suggests a creatable
    default: when the folder name is already a project in the selected team, it
    suggests <folder-name>-<short suffix> instead of a name that can only fail
    "Project already exists" validation.
  • 176d939: Add vercel vcr login [engine] to authenticate docker, podman, or buildah with the Vercel Container Registry using an OIDC token.
Patch Changes

  • 2522d0a: [ai-gateway] add models ls and models endpoints commands

  • 8e93bc1: Fix vc build behavior in an unlinked directory. The link flow now runs before the "Run vercel pull?" prompt instead of firing as a side effect of the pull, and the freshly-established link is picked up on the same run — previously the first build computed a wrong work path (e.g. apps/api/apps/api) that only corrected itself on a subsequent run.

  • 6b93f07: Add per-Builder install reasons to the vc.installBuilders trace span, distinguishing Builders that are not installed from ones whose entrypoint fails to load and from explicit version or range mismatches

  • 8f10c0b: Ask interactive vercel link users to choose a team before project discovery,
    add searchable team and existing-project pickers, and allow Escape to cancel
    prompts cleanly. After team selection, the project picker prioritizes projects
    linked to the local Git repository with the matching Root Directory, then falls
    back to an exact folder-name match before offering full project search or
    project creation. Git matches persist the repository mapping in
    .vercel/repo.json. The project-name prompt allows Up to return to the picker,
    and project selection and search provide choices for returning to the previous
    step. Explicit --scope and --team values skip the team prompt and restrict
    project lookup to that team.

  • f03f001: Stopped showing the "Update available … Would you like to upgrade now?" prompt immediately after running vercel upgrade. The running process still holds the pre-upgrade version in memory, so the notifier would ask the user to upgrade again right after a successful upgrade.

  • f03f001: vercel upgrade no longer classifies the installation as local without positive evidence (a lockfile found above the CLI's install location). Previously, when the installation layout was not recognized, the upgrade defaulted to running npm i vercel@latest in the current working directory — silently adding vercel to whatever project (or home directory) the user happened to be standing in. Unrecognized layouts now degrade to a global npm upgrade, which runs from a temporary directory and cannot modify the current project.

  • f03f001: Fixed vercel upgrade misdetecting pnpm 11 global installs as local npm installs. pnpm 11 moved global packages to isolated directories under PNPM_HOME/global/v11/ backed by the global virtual store, which the previous detection did not recognize — causing the upgrade to run npm i vercel@latest in the current working directory (creating a stray node_modules) while reporting success without upgrading the real installation. Detection now recognizes installs running from inside PNPM_HOME, and no longer crashes when the entrypoint path cannot be resolved on disk.

  • 8d25cea: Apply functions configuration (memory, maxDuration, architecture, regions, functionFailoverRegions, experimentalTriggers, supportsCancellation) to container runtime outputs. The @vercel/container builder now resolves matching vercel.json / per-service functions entries at build time, and the CLI writes those settings into the container .vc-config.json.

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

  • 456d388: Add CLI support for managing conditional feature flag rules.

    Example command runs:

    vercel flags rules ls my-feature --environment production
vercel flags rules ls my-feature --environment production --json
vercel flags rules add my-feature --environment production --condition user.plan:eq:pro --variant on
vercel flags rules add my-feature --environment production --condition segment:eq:seg_beta123 --variant on
vercel flags rules add my-feature --environment production --condition user.plan:eq:pro --by user.userId --weight off=90 --weight on=10 --position 1
vercel flags rules update my-feature rule_123 --environment production --condition user.plan:eq:enterprise
vercel flags rules update my-feature rule_123 --environment production --variant off
vercel flags rules move my-feature rule_123 --environment production --position 1
vercel flags rules remove my-feature rule_123 --environment production

  • d213d27: Include build logs in vercel inspect --logs --format json output.

  • 3b98912: Add --limit support to additional paginated CLI list commands and preserve next-page hints when custom limits are used.

  • 8f10c0b: Skip the Which team? prompt when the account has exactly one team choice
    (for example a token scoped to a single team). The resolved team is shown as
    an aligned Team row instead, and the project picker hides
    Choose a different team when there is no other team to choose. Team picker
    labels now match vc switch: Name (slug), a bold (current) marker, and a
    lock for teams that require SSO.

  • 5b29d19: Forward alert rule scope and format flags to nested subcommands.

  • 7b30856: Add vercel dev support for Python queue subscribers defined in pyproject.toml.

  • c556d0d: Fix vercel upgrade on pnpm installs: pnpm v10+ requires approval to run dependency build scripts (e.g. esbuild's postinstall) and would prompt or skip them during the upgrade. Global pnpm upgrade commands now pre-approve the required build script via --allow-build, which applies to that single install only and persists no policy.

  • Updated dependencies [8d25cea]

  • Updated dependencies [6b2cfc6]

  • Updated dependencies [0f67a94]

  • Updated dependencies [dbefe95]

  • Updated dependencies [89ef74f]

  • Updated dependencies [8b36776]

  • Updated dependencies [e12b1bd]

  • Updated dependencies [7b30856]

v54.21.1

Compare Source

Patch Changes
  • 1e774e8: Preserve generated service routes when Build Output services are merged from framework output into a custom build output directory.
  • c9c9edb: Add --project support to project-scoped flags, cache, crons, and rolling-release commands.

v54.21.0

Compare Source

Minor Changes

  • cc74129: Enable monorepo subdirectory build fixes by default (previously gated behind VERCEL_RESOLVE_ROOT_DIRECTORY=1), scoped to directories the workspace actually claims.

    When a project is linked in place (apps/api/.vercel/project.json) and vc build is run from that directory, the build now re-anchors to the workspace root and expresses the project as its path relative to that root — so builders trace correctly, hoisted dependencies are packaged, and --standalone output preserves package-manager symlinks so dependencies resolve at runtime.

    Re-anchoring only happens when an ancestor workspace manifest (pnpm-workspace.yaml or package.json#workspaces) actually declares the linked directory as a member package. Membership is decided by matching the directory's path against the manifest's declared patterns (including negations like !apps/legacy) plus a package.json existence check — pure string matching with no filesystem traversal, so large repositories and recursive patterns like ** cost nothing. A project that merely sits inside an unrelated repository — a vendored folder, a fixture, a scratch project in a company monorepo, or a plain git repo with no workspace — is left untouched and builds from its own directory exactly as before.

    The rootDirectory setting is interpreted relative to the link's location and honored when it points at a folder that exists; otherwise (e.g. a redundant apps/api setting on a link at apps/api, which previously crashed with ENOENT .../apps/api/apps/api/...) it is ignored in favor of the link's own location and a warning is emitted.

    To restore the previous behavior, pin an earlier CLI version.

Patch Changes
  • 001a879: Do not duplicate global flags (e.g. --scope) in agent-output next[] command suggestions when the command template already carries the flag
  • d15f17c: Resolve projects for domains inspect and domains rm from the domain's project-domains instead of scanning every project in the account
  • 3190211: Show list help instead of transfer-in help for vercel domains ls --help
  • 85c897e: Run framework detection during vc build (opt-in via VERCEL_FRAMEWORK_DETECTION=1): detect the framework on a project's first deployment (VERCEL_FIRST_DEPLOYMENT=1) when none is configured and record it as detectedFramework in builds.json, cross-check the configured framework against the source code in the background without slowing the build, and validate the build output after it is written. Adds a detectionConfidence annotation to framework definitions for detections that are commonly incidental (e.g. Storybook as a devDependency) so they are never suggested as a framework override.
  • 3f3ca56: [cli] integration add now installs a product's declared agent skills after provisioning. It reads the product's agentSkills (public GitHub SKILL.md links) and runs npx skills add for each — prompting first in an interactive terminal (default yes), or auto-installing for non-interactive callers (agents, CI). --format=json stays read-only: it surfaces a skills array instead of installing. Non-GitHub or unparseable links are skipped.
  • 3aa331b: Emit structured agent-output JSON (project_not_found with runnable next suggestions) when vercel list <project> does not resolve in non-interactive mode
  • 24b012c: Update the CLI's sandbox dependency from 3.1.2 to 3.4.0.
  • d8307a7: Add a project update command for changing framework and build settings.
  • Updated dependencies [6dbc280]
  • Updated dependencies [4097a62]

v54.20.1

Compare Source

Patch Changes
  • 4b1306c: List vercel agent-runs in the root CLI help output.
  • 0b64f51: Add missing commands to the root vercel --help list: ai-gateway, edge-config, oauth-apps, sandbox, and tokens

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

✂ Note

PR body was truncated to here.

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.

@renovate renovate Bot force-pushed the renovate/vercel-56.x branch from 4c3d406 to 9001568 Compare July 13, 2026 23:54
@renovate renovate Bot force-pushed the renovate/vercel-56.x branch from 9001568 to 17642e4 Compare July 14, 2026 18:35
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