Skip to content

Update dependency vercel to v54#31

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

Update dependency vercel to v54#31
renovate[bot] wants to merge 1 commit into
v2from
renovate/vercel-54.x

Conversation

@renovate

@renovate renovate Bot commented May 13, 2026

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^54.0.0 age confidence

Release Notes

vercel/vercel (vercel)

v54.12.1

Compare Source

Patch Changes

v54.12.0

Compare Source

Minor Changes
  • 5757bca: [services] add support to vc dev for experimentalServicesV2.
Patch Changes

v54.11.1

Compare Source

Patch Changes

v54.11.0

Compare Source

Minor Changes
  • fc7b557: Ensure project manifest includes framework for non-service builds.
Patch Changes
  • bc8dc95: Fix the darwin-arm64 native CLI binary crashing with SIGSEGV on most commands. The custom Node
    runtime was stripped with bare strip, which removes the exported napi_* symbols that native
    addons (@napi-rs/keyring) bind against at dlopen time. The runtime is now stripped with
    strip -SXx, which keeps exported symbols. Also makes the @vercel/vc-native bin shim launch
    the platform binary directly when the postinstall script did not run (pnpm blocks dependency
    build scripts by default), instead of always failing.
  • bc8dc95: Fix vercel upgrade crashing with ENOENT: no such file or directory, realpath '…/.pkg-staging/pkg.js'
    in the native binary. The command tried to realpath process.argv[1], which points into the binary's
    virtual filesystem snapshot. Native installs now detect the package manager (npm, pnpm, or yarn) from
    the binary's real install location and suggest the matching global upgrade command.

v54.10.3

Compare Source

Patch Changes
  • 4f82914: Bump the embedded sandbox CLI to 3.1.2 (@vercel/sandbox 2.1.1) to fix vc sandbox commands crashing with a segmentation fault.

v54.10.2

Compare Source

Patch Changes
  • 0f7844c: Fix the native CLI binary crashing on auth commands (login, whoami, logout, and any
    command that reads config) with ERR_MODULE_NOT_FOUND: '@​vercel/cli-auth'. The package is now
    staged into the binary. The binary release is also hardened with a real command smoke test and a
    build-time check that every statically-imported dependency is bundled, so a binary missing a
    required package can no longer be released.
  • Updated dependencies [78e5d4f]

v54.10.1

Compare Source

Patch Changes

v54.10.0

Compare Source

Minor Changes
Patch Changes
  • f6a6e55: Only offer the Claude Code plugin in projects that have actually been used with Claude Code. Previously the prompt could appear in any directory as long as a ~/.claude directory existed on disk. The CLI now checks whether the current project (walking up from the working directory) appears in Claude Code's per-project history before offering the plugin.

  • a4f7dc9: CLI help and command-schema cleanups from the docs audit:

    • blob: remove orphan addStoreSubcommand, removeStoreSubcommand, and getStoreSubcommand exports that duplicated the wired create-store / delete-store / get-store specs. Handlers and telemetry now import the actual wired subcommand definitions.
    • dns list: the <domain> argument is now declared required: false to match the runtime, which already supports listing every domain's records when no argument is given.
    • routes delete: declare the <name-or-id> argument as multiple: true so the help synopsis and schema match the variadic behavior already supported by the handler and shown in the existing examples.
    • init: fix the "Initialize example project into specified directory" help example, which was missing the init literal (vercel <example> <dir>vercel init <example> <dir>).
    • promote status and rollback status: declare --timeout on the status subcommand options so --help matches the examples (promote status --timeout 30s, rollback status --timeout 30s). The flag is also kept on the parent command, where parsing actually happens.
  • 33efa25: Added non-managed Connex connector creation with --data and optional --connector-type.

  • 3a2d61e: Add vercel domains search <query> for client-side Domain Discovery with fast bulk availability and registrar pricing, renewal pricing, --available and exact TLD filters, ordering, candidate windows of up to 200 domains, and JSON output.

  • c5eeb30: Gate the client-side 900-second maxDuration upper bound behind the VERCEL_CLI_SKIP_MAX_DURATION_LIMIT environment variable. The limit is now owned by a single helper in @vercel/build-utils instead of being hardcoded in multiple validators. When the variable is set to 1, the client-side maximum is skipped and validation defers to the server. Default behavior is unchanged — the maximum, the lower bound, and the integer check are all still enforced when the variable is unset.

  • 9f9eed3: Nest Build Output API files for experimentalServicesV2 under .vercel/output/services/<name>.

  • fb30b76: Strip ANSI escape sequences from connector UID and name cells in connect list table output.

  • Updated dependencies [c5eeb30]

  • Updated dependencies [09c39af]

v54.9.1

Compare Source

Patch Changes
  • f5ab607: [evals] Shrink eval result uploads and fix run discovery

    The eval ingest transform (transform-agent-eval-to-canonical.js) now excludes raw transcripts (transcript-raw.jsonl) from the --upload-artifacts all path, roughly halving each ingest payload. The parsed transcript.json is still uploaded and still read for resolvedModels metadata.

    It also normalizes provider-prefixed model paths before upload. Models that resolve to provider/model (e.g. openai/gpt-5.5-pro) write results one directory deeper, pushing the timestamp past the experiment/model/timestamp shape the ingest endpoint discovers runs from, which previously failed with Could not discover any experiment/model/timestamp runs. The model is now collapsed to a single segment (openai-gpt-5.5-pro) so discovery succeeds.

  • 2b31813: Fix vc build --standalone failing to zip Lambdas when run from a monorepo
    subdirectory. When dependencies are hoisted to the monorepo root (e.g. pnpm's
    node_modules/.pnpm/...), the recorded function file paths could escape the
    function root (../../node_modules/...), which later caused zipping to fail
    with invalid relative path: ../../node_modules/.... These paths are now
    re-anchored inside the function so the standalone output is self-contained.

  • 252c6eb: [cli] Show claim in vercel integration resource --help

    The claim subcommand was missing from resourceSubcommand.subcommands, so vercel integration resource --help only listed connect, disconnect, remove, and create-threshold. The legacy vercel integration-resource --help and the dispatcher's runtime resolution both already included claim — this was purely a help/discoverability gap on the canonical nested path. Adds claimSubcommand to the subcommand list and updates the parent description accordingly.

  • 0a170fd: [services] wire experimentalServicesV2 into fs-detectors.

  • Updated dependencies [aeb5bfa]

  • Updated dependencies [0a170fd]

v54.9.0

Compare Source

Minor Changes
  • fb4fb2d: Add support for claiming sandbox marketplace resources (Stripe, Shopify) from the CLI. integration list shows a new Claim column, integration-resource claim <name> opens the provider claim URL in the browser and polls until completion, and integration add offers to claim sandbox resources after provisioning with new --claim / --no-claim flags.
Patch Changes

v54.8.0

Compare Source

Minor Changes
  • fddeb55: Add configurable credentials storage handling across the CLI auth stack. Storage of credentials can be configured by the new credStorage key in global config.json or the new VERCEL_TOKEN_STORAGE environment variable. The environment variable takes precedence over the configuration key. Accepted values are file (store credentials in auth.json), keyring (store credentials in system keyring, e.g macOS Keychain or Secrets Service on Linux), and auto (try storing in keyring if available, fall back to file if keyring is not available).

    @vercel/oidc supports keyring-stored authentication credentials by delegating the OIDC minting to the CLI executable via @vercel/cli-exec.

Patch Changes
  • a869874: [connect] Rename user-facing "client" references to "connector"

    Updates the vercel connect CLI commands to use the official "connector" terminology in all user-facing surfaces: help text argument names (remove/attach/detach), usage strings in error messages, and the --format=json output key (clientsconnectors) for vercel connect list.

  • 200aa3b: [connect] Forward --scopes and --installation-id into the authorize/install recovery URL

    When vercel connect token hits an action-required error (user_authorization_required or client_installation_required), the CLI builds an authorize/install URL for the user to complete consent in the browser. Previously this URL carried only teamId and request_code, dropping the --scopes and --installation-id the user supplied. As a result the consent flow fell back to provider defaults (e.g. Slack's users.profile:read), and the post-authorization token retry mismatched the requested scopes. The CLI now forwards scopes (comma-joined) and installationId as query params, which the authorize and install endpoints already accept.

  • 3019788: [services] Remove the services field from vercel.json and the VERCEL_USE_SERVICES gate.

  • fe893ec: [services] Add experimentalServicesV2 field to vercel.json implementing the new schema for services.

  • d22d812: [cli] Nest integration-resource under integration resource and add integration resource connect

    The marketplace resource subcommands (disconnect, remove, create-threshold) are now discoverable under vercel integration resource <sub>. The standalone vercel integration-resource and vc ir forms still work as hidden aliases — no scripts or tests break.

    Adds a new vercel integration resource connect <resource> [project] command (the inverse of disconnect). Accepts --environment (repeatable, defaults to all three), --prefix for env var namespacing, --yes, and --format=json. Defaults to the project linked in the current directory when <project> is omitted.

    Tightens disconnect to error (exit 1) when the specified project is not connected to the resource, instead of exiting 0 with a "not found" message.

    Both commands emit a structured outputAgentError payload with reason: confirmation_required and a next: [{command}] retry hint when run in non-interactive / agent mode without --yes. When connect fails because an env var with the same name already exists on the target project, the error names the conflicting variable and suggests --prefix or vercel env rm as remediation.

  • Updated dependencies [3019788]

  • Updated dependencies [fe893ec]

  • Updated dependencies [fddeb55]

v54.7.1

Compare Source

Patch Changes

v54.7.0

Compare Source

Minor Changes
  • 0b4e1ef: Add vercel connect revoke-tokens subcommand to revoke tokens issued from a connector.
Patch Changes
  • ba6e7c6: Internal: fix _deploy eval grader passing --token "" in the Docker sandbox where VERCEL_TOKEN isn't in process env. Only pass --token when set; CLI falls back to auth.json otherwise.
  • 92988c2: Handle sensitive Environment Variable pull challenges in the CLI.
  • 3986bb0: Stop retrying intentionally aborted requests so the CLI exits promptly after a deployment is ready.
  • 64f5484: Allow SAML re-authentication to use device-code flow in non-TTY sessions.
  • 97fdbbe: [flags] fix dep detection for build embedding
  • Updated dependencies [2d918b8]

v54.6.1

Compare Source

Patch Changes

v54.6.0

Compare Source

Minor Changes
  • af3e0bd: adding version node + cli version to top of every command
Patch Changes

v54.5.1

Compare Source

Patch Changes

v54.5.0

Compare Source

Minor Changes
  • 6860c32: Add project manifest to rust builder.
  • 2c17a12: Added --open and --view flags to vercel traces get. --open opens the trace in the Vercel Dashboard instead of printing the markdown summary. --view <timeline|tree|gantt> selects the dashboard view and is only valid with --open.
Patch Changes

v54.4.1

Compare Source

Patch Changes

v54.4.0

Compare Source

Minor Changes
  • 9d9532d: Wire builder entrypoint detection into service setup.
Patch Changes

v54.3.0

Compare Source

Minor Changes
  • 8fabeba: vercel curl --trace now sends the _vercel_session cookie alongside the trace cookie, scopes the session API call via query parameters, sends hostname instead of deploymentId, and parses the request id from the x-vercel-id response header.

  • f2c60d6: [vercel-flags] check flags pkgs for build embedding

  • 8ac2af6: Add --project <NAME_OR_ID> flag to build, deploy, pull, and dev for non-interactive CI/CD and agent-driven use.

    When --project is provided, the CLI will:

    • Disambiguate monorepo .vercel/repo.json linked projects without prompting (matches by name or ID)
    • Resolve the project via the API when no local link is present
    • Fail fast with a clean "Project ... was not found" error if the value cannot be resolved (never silently creates a new project)
    • In non-interactive contexts (CI, agents) the same failure also emits a structured JSON payload with a next array of suggested follow-up commands.

    This is particularly important for agents (which run non-interactively by default): they can now target a specific project in monorepos and unlinked directories without relying on interactive setup prompts or the project picker.

    The flag is also accepted on vercel deploy init (excluded on vercel deploy continue because --id already identifies the deployment).

    The new API-based resolution is opt-in via the explicit --project flag, so commands like vercel deploy in an unlinked directory keep their existing behavior of falling back to interactive setup.

  • a2e79a8: Added vercel traces get <request-id> to fetch and render a trace summary for a request. Resolves project/team from the linked project, with --scope and --project flag fallbacks.

Patch Changes
  • b0d4dba: Add OIDC auth support to vercel blob commands and upgrade @vercel/blob to 2.4.0. When VERCEL_OIDC_TOKEN and BLOB_STORE_ID are set in the environment (or .env.local), or when --oidc-token and --store-id are passed together, the CLI uses them as the credential source. The --rw-token flag remains exclusive — when provided, it always wins and never falls back to OIDC. The OIDC token is now forwarded to the SDK via the native oidcToken option (added in @vercel/blob 2.4.0) rather than by mutating process.env.

  • c6fa2d1: Revert non-interactive Marketplace terms acceptance for integration accept-terms.

    This change requires human interactive confirmation for terms acceptance and removes --yes from integration accept-terms guidance.

  • a5b231a: Update vercel env pull to add .env* to .gitignore for default .env.local pulls.

  • Updated dependencies [e6dc048]

  • Updated dependencies [2cd64ea]

  • Updated dependencies [23eee91]

  • Updated dependencies [79d9508]

v54.2.0

Compare Source

Minor Changes
  • 39850ef: Add vercel connect update <id> subcommand to change connector branding. Accepts --icon (PNG or JPEG path, uploaded to Vercel and sent as SHA-1), --background-color, and --accent-color (both #RRGGBB). Gated behind the existing FF_CONNEX_ENABLED flag.
  • 63a66d4: Add --icon, --background-color, and --accent-color flags to vercel connect create. The icon is uploaded to Vercel before the connector is created. When the API requires a browser registration step, branding is appended to the dashboard URL so the create form can prefill itself; the CLI also applies a follow-up PATCH after the browser flow as a safety net for the dashboard rollout. Gated behind the existing FF_CONNEX_ENABLED flag.
  • 137e5d1: Allow builder V2 to expose startDevServer.
  • b1aa926: [vc dev] handle process errors in dev server
Patch Changes
  • a3a1a5a: Added CLI eval support for comparable agent/model experiment runs and restored transcript artifact uploads via chunked result ingestion.

  • 18e9fd6: fix(cli): point vc connect open and registration error URLs at the renamed /connect dashboard route

  • 4118600: Fix standalone CLI binary latest-version worker startup.

  • 80e8e06: Track Vercel plugin active-session markers in CLI telemetry.

  • bb61428: Include framework slug in output/config.json

  • f45e466: Add opt-in automatic CLI updates via vercel upgrade --enable-auto and prompt users to enable them after a successful manual upgrade.

  • a3a1a5a: Add offline-friendly local modes for CLI eval discovery and dashboard fixture generation, and expand Vercel CLI eval coverage for project, list, inspect, logs, and pull commands.

  • a3a1a5a: Relaxed the CLI env/add eval grader to accept equivalent JSON format syntax and shell-variable env names w

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-54.x branch 6 times, most recently from a53ac31 to eb2a5ad Compare May 22, 2026 21:05
@renovate renovate Bot force-pushed the renovate/vercel-54.x branch 6 times, most recently from 5e5df51 to b735d0d Compare June 2, 2026 00:40
@renovate renovate Bot force-pushed the renovate/vercel-54.x branch 8 times, most recently from 7d52501 to f45ad8c Compare June 10, 2026 13:13
@renovate renovate Bot force-pushed the renovate/vercel-54.x branch from f45ad8c to 2dffa0c Compare June 11, 2026 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants