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
Copy link
Copy Markdown
Contributor

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

ℹ️ 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.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 when outputs prove the variable was added.

  • a3a1a5a: Simplified the implicit curl eval grader to only require that the agent ran vercel curl or vc curl.

  • 8fb4dc8: Add vercel flags split to configure weighted Vercel Flags splits from the CLI.

    Configure a split interactively by letting the CLI prompt for the environment, bucketing attribute, weights, fallback variant, and revision message.
    vercel flags split welcome-message

    Configure a boolean flag split in production with 95/5 traffic.
    vercel flags split redesigned-checkout --environment production --by user.userId --weight off=95 --weight on=5

    Configure a string flag split with an explicit fallback variant.
    vercel flags split welcome-message -e production --by user.userId --default-variant control --weight control=90 --weight treatment=10

    Exclude a variant from receiving traffic by setting its weight to 0.
    vercel flags split checkout-copy -e preview --by user.userId --default-variant control --weight control=50 --weight treatment=50 --weight legacy=0

  • Updated dependencies [bb61428]

  • Updated dependencies [137e5d1]

  • Updated dependencies [f45e466]

  • Updated dependencies [744e96c]

  • Updated dependencies [7923d34]

v54.1.0

Compare Source

Minor Changes

  • 9aead7a: Add vercel connect detach to detach a Vercel project from a connector via DELETE /v1/connect/connectors/:id/projects/:projectId. Mirrors vercel connect attach and matches the project-scope "Disconnect" button in the dashboard.

    Add --triggers, --trigger-branch, and --trigger-path flags to vercel connect attach. When --triggers is set, the project is also registered as a trigger destination on the connector via PATCH /v1/connect/connectors/:id/trigger-destinations so verified webhooks get forwarded to it. Requires the connector to support triggers; warns if the connector was created without triggers.enabled.

    Both features gated behind the existing FF_CONNEX_ENABLED flag.

  • b1db109: Enable vercel connect by default and mark it as beta in --help. The command was previously gated behind the internal FF_CONNEX_ENABLED env var; it is now available out of the box and surfaces in vercel --help as connect [cmd] Manage connectors [beta]. The subcommand description also reads Manage connectors (Beta).

    Fix vercel connect open to link to the renamed /~/connect/ dashboard route directly instead of relying on the legacy /~/connex/ → /~/connect/ 308 redirect.

  • e8deaa1: Rename vercel connex command to vercel connect. The command remains gated behind the existing FF_CONNEX_ENABLED flag.

  • cc30efd: Refresh the vc setup-and-link flow and post-deploy output for clarity and visual consistency.

    Prompt copy

    • Want to modify these settings? → Customize settings?.
    • Which scope should contain your project? → Which team?. Matches dashboard + docs vocabulary.
    • What's your project's name? → Name?. The directory-derived default still renders inline via the inquirer default.
    • Loading scopes… spinner → Loading teams….

    Flow changes

    • Removed the Set up and deploy "/path"? confirmation prompt. Intent is implied by running vc; the path is surfaced as a status line ( Set up "/path") and Ctrl-C remains the escape hatch.
    • The In which directory is your code located? prompt now fires when (a) the current directory is a workspace (monorepo with multiple packages), (b) the user explicitly chose "Choose a different root directory" via the inferred-services picker, or (c) framework detection at the root finds nothing — covers nested-monolith layouts like repo/app/package.json where the app lives in a subdir. Single-app projects with a framework detected at the root still default the root to . and skip the prompt.

    Output format

    • Auto-detected Project Settings for X line replaced with a single bold Detected X (Build Command: …, Output Directory: …) line. Title Case labels match the checkbox panel below. Only Detected is bold; framework name and parens render plain/dim.
    • Introduced a new aligned-label format for status output via the printAlignedLabel helper (12-char bold label column, value column at terminal column 14). Applied to Linked / Inspect / Production / Preview / Aliased / Added rows.
    • vc redeploy output now uses the same aligned-label format as vc deploy — Inspect / Production / Preview / Aliased rows are consistent across both commands. No more emoji-prefix / aligned-label mixing in the same session.
    • vc link --repo info messages (No Projects are linked…, Found N Project(s) linked…, Detected N new Project(s)…, Created new Project: …) dropped the gray > prefix and now use the 2-space indent that matches the rest of the link/setup flow.
    • Path-in-prompt for vc link --repo confirm message uses chalk.dim instead of chalk.cyan — paths are not URLs, so dim is the correct treatment per the color rules (cyan reserved for URLs).
    • Introduced a "gutter" semantic system: column 0 is reserved for semantic glyphs. ▲ marks Production deploys (▲ Production URL) and breaks out of the indent — bookending the session with the ▲ brand mark at the top. Preview deploys stay in-column without the triangle.
    • Added a terminal ✓ Ready in Xs line at deploy completion (green ✓ at column 0, bold Ready, dim duration). Skipped when --no-wait is set and the deployment hasn't reached READY yet.
    • Dropped the emoji prefixes (🔗, 🔍, ⏳) on Linked / Inspect / Production rows (across both vc deploy and vc redeploy).
    • Dropped the Building: prefix from the build-logs spinner. Each streamed log line is shown verbatim instead of Building: <line>.
    • Dropped the (created .vercel and added it to .gitignore) parenthetical from Linked — git status surfaces it on demand.
    • Dropped the [Xs] timing suffix from URL lines. URLs are results, not operations — timing belongs on the build / ready signal.

    Defensive fix

    • services-setup.ts now uses an optional chain on detectServicesResult.resolved?.source. This was crashing the setup flow before any prompts could fire when no services were detected (common for empty or simple fixtures).

    New helper

    • packages/cli/src/util/output/print-aligned-label.ts exports printAlignedLabel(label, value, options?: { gutter?: string }) and the ALIGNED_LABEL_WIDTH constant (12). Used by every aligned-row print site.

  • 4fc110b: [services] add preDeployCommand for experimentalServices

Patch Changes

v54.0.0

Compare Source

Major Changes
  • db207b1: Require --follow for vercel logs to stream deployment logs. Passing a deployment argument or --deployment now uses historical deployment log filtering by default.
Minor Changes
  • d874af6: Add support for env vars injection that reference other services in services with an explicit env configuration.
Patch Changes

v53.4.0

Compare Source

Minor Changes
  • 88fb6c1: Add vercel connex attach <client> to attach a Vercel project to a Connex client for one or more environments. Defaults to the current linked project + all environments (production, preview, development). Pass -e/--environment (repeatable, comma-separated) to restrict, -p/--project <name_or_id> to target a different project, and --yes / --format=json for non-interactive use. When the project is already attached with the same environments, the command exits early as a no-op; when the environments differ, the prompt shows a current-vs-new diff before replacing.
  • 66a2105: vercel dev now exposes VERCEL_PROJECT_ID and VERCEL_ORG_ID from the linked .vercel/project.json to the dev process, mirroring how the platform sets them in prod and preview. Existing values in process.env or .env files take precedence and are not overridden.
Patch Changes

v53.3.2

Compare Source

Patch Changes

v53.3.1

Compare Source

Patch Changes

v53.3.0

Compare Source

Minor Changes
  • dbfcc04: vercel connex list now defaults to clients linked to the current project. When no project is linked, it falls back to listing every Connex client in the team (same as --all-projects). Use --all-projects to force the team-wide view; the table includes a Projects column with the linked project names per client (with a + more suffix when truncated).
  • 3b368bd: Add --format=json support to vercel project token, direct token output to stdout instead of stderr.
  • 34f595a: Extract CLI global config and auth config helpers into new @vercel/cli-config, use @effect/schema for config validation.
  • b4ada64: Implement scheduled jobs for JS/TS.
Patch Changes

v53.2.0

Compare Source

Minor Changes
  • 3898acb: Add vercel firewall command for managing project firewall configuration. Supports custom rules (add, edit, delete, enable, disable, reorder), IP blocking, system bypass rules, attack challenge mode, and system mitigations.
Patch Changes
  • 0cf132c: vercel connex create now accepts a --triggers flag. When passed, the request body includes triggers: { enabled: true } so the server wires webhook triggers into the created client. Without the flag, triggers: { enabled: false } is sent.
  • 1d766af: Let --yes enable the browser recovery flow for vercel connex token even in non-TTY contexts (e.g., coding agents), so a single command can open the browser, poll, and return the token without round-tripping through the agent's chat.
  • dd27e25: Added vercel deploy continue --error to mark manual deployments as failed with an optional error message.
  • 2f2b3f1: Added --filter/-f <NAME> flag to vercel project ls for filtering projects by name (substring match).
  • b2c2541: Avoid resolving the configured default team before unscoped vercel link --yes --project cross-team search, so team-scoped tokens can still link projects they can access.
  • 5f3cf99: Skip SAML-protected ("limited") teams during vercel link's cross-team auto-detect so it no longer forces device-code re-authentication for scopes the user did not explicitly choose. The project is still linked from any accessible team where it's found, and limited scopes remain available through the standard scope picker (selectOrg) or --scope <slug>.

v53.1.1

Compare Source

Patch Changes
  • 4a5be0b: Fixed vc env update failing when updating sensitive environment variables.
  • 2ffd7bc: Tighten the SdkKey type so plaintext keyValue, tokenValue, and connectionString can no longer appear on list responses. flags sdk-keys ls --json already omitted these via an explicit allowlist; the type split makes the guarantee static. Create-time output from flags sdk-keys add is unaffected.
  • e6cb5bc: Hide --token from help output for commands that don't support it (login, switch).
  • 8a5aa6a: Ensure synthetic SPA fallbacks are merged after builder-produced routes.
  • bab5a60: Handle stale Claude Code Vercel plugin registry entries during plugin migration.
  • Updated dependencies [34e7b09]
  • Updated dependencies [8e29c9c]
  • Updated dependencies [2da36f3]
  • Updated dependencies [fa5f57a]
  • Updated dependencies [97f87f7]

v53.1.0

Compare Source

Minor Changes
  • 5cf1179: Use services orchestrator for single web services in local dev.
Patch Changes
  • 3aa821e: Allow adding Development Environment Variables on teams that enforce sensitive Environment Variables.

v53.0.1

Compare Source

Patch Changes

v52.2.1

Compare Source

Patch Changes
  • bf07448: Revert "auth: Make it possible to store CLI credentials in OS keychain (#​16083)"
  • a00740e: vc whoami now shows both the logged-in user and the active team, and surfaces when the active team is set by a local project link rather than the globally-selected team.
  • Updated dependencies [894e7d4]

v52.2.0

Compare Source

Minor Changes
  • 24686d0: Add configurable auth token storage with keyring-backed persistence and file fallback support.
Patch Changes

v52.0.0

Compare Source

Major Changes
  • fix!: exclude configuration files from static deployments (#​16056)
Minor Changes
  • Add vercel connex token command to fetch tokens for Connex clients, with auto-authorize / auto-install recovery on actionable 422 errors. (#​16072)
Patch Changes

v51.8.0

Compare Source

Minor Changes

  • vercel env add now defaults Environment Variables to sensitive on Production and Preview. Sensitive values are encrypted at rest and cannot be retrieved later via the dashboard or CLI; they are still resolved for builds, deployments, vercel env pull, and runtime. (#​16041)

    Behavior per target:

    • Production or Preview: defaults to sensitive. Pass --no-sensitive to opt back in to the previous encrypted behavior (value remains readable later).
    • Development: always stored as encrypted (sensitive is not supported by the Vercel API for Development). Passing --sensitive alongside a Development target now errors up-front instead of silently falling back.
    • Mixed selection (e.g., interactive checkbox picks production + preview + development): errors and asks you to run vercel env add separately for Development, because Development cannot share a record type with Production/Preview.

    Flag summary:

    • --sensitive: unchanged in meaning (request a sensitive variable); now errors when combined with Development.
    • --no-sensitive: new; opt out of the new default for Production/Preview.
    • --sensitive --no-sensitive together: errors.

    On teams that enable the "Enforce Sensitive Environment Variables" policy in team settings, the CLI now reads the policy from the team object and notes in the output that the policy is active; the server already promotes Production/Preview variables to sensitive silently, and the CLI's own logs are now honest about it. Passing --no-sensitive on a policy-on team for Production/Preview now emits a warning — the flag is a no-op because the server promotes the variable regardless — and the CLI sends type: 'sensitive' so its own --debug output matches what gets stored.

Patch Changes

v51.7.0

Compare Source

Minor Changes

  • [detect-services] If a vercel.toml exists, update the vercel.toml (#​15895)

  • Use correct filename in messages when config file is not vercel.json (#​15893)

  • [services] move Python workers to v2beta triggers with private routing (#​15920)

Patch Changes

v51.6.1

Compare Source

Patch Changes

v51.5.1

Compare Source

Patch 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-54.x branch 5 times, most recently from 877e008 to a53ac31 Compare May 22, 2026 15:06
@renovate renovate Bot force-pushed the renovate/vercel-54.x branch from a53ac31 to eb2a5ad Compare May 22, 2026 21:05
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