chore(deps): update dependency vercel to v56#3854
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
55.0.0→56.1.0Release Notes
vercel/vercel (vercel)
v56.1.0Compare 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 initno longer materializes symlink or hardlink entries from downloaded example archives (blocking tar link-following path traversal, CVE-2024-12905 / CVE-2025-48387, and upgradingtar-fsto 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, andai-gateway coding-agents setupnow 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.0Compare Source
Major Changes
4998ec8:vercel routes exportnow uses--output(-o) instead of--formatto select the output file format (jsonorts, dotted forms like.tsalso accepted). This frees--formatto align with the standard output-format convention used by other commands. Update any scripts fromroutes export --format tstoroutes export --output ts.Minor Changes
5ae15fa: Addvercel ai-gateway coding-agents setupto 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(honoringCLAUDE_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 aftervercel integration addprovisions 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 manualnpx skills addcommand.607f0ef: Add service information to deploy-manifest.8642a47: Remove thevercel oauth-appssub-command, reverting the OAuth / connected apps parity scope.57e2091:vercel env pullnow 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_TOKENand analytics IDs) are still removed when they no longer exist upstream.Patch Changes
2a403e2: Add Codex support tovercel ai-gateway coding-agents setup. It writes avercelmodel provider to~/.codex/config.toml(OpenAI-compatible base URL,responseswire API) without pinning a default model, and exports the gateway API key via your shell rc (honoringCODEX_HOMEand fish/ZDOTDIR). Merging into an existingconfig.tomledits assignments in place, preserving your comments and formatting.683f013:ai-gateway coding-agents setupcan now provision a key for you: run it without--keyand it creates an AI Gateway API key (prompting for the owning team and a name, or using--name/--scopeand 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
--reconfiguredoes 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 setupnow 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--yesruns configure Codex only when it is explicitly requested with--agent/--all; JSON output gains awarningsarray and arequires_consentskip reason, and a run refused for lack of consent exits 1 with a self-containedrequires_consenterror payload (structured warnings, skip entries, and a runnablenext[]command). A declined agent's configuration is left untouched.7190684:ai-gateway coding-agents setupnow 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-rcis passed explicitly). Non-interactive re-runs with--keyon an already-configured macOS Keychain setup now refresh the stored key instead of silently keeping the old one.097395b:ai-gateway coding-agents setupcan now put limits on a key it creates: a spend cap (--budgetwith--refresh-period/--include-byok) and an expiry (--expiration7d|30d|60d|90d|1y|none). Interactively it asks whether to set each. The limits are sent only when creating a key; reusing one with--keyis unaffected.fcdf5cd: Store thecoding-agents setupAPI 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 runssecurity 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 tovercel ai-gateway coding-agents setup. It supplies the gateway API key to OpenCode's nativevercelprovider in~/.config/opencode/opencode.json(honoringXDG_CONFIG_HOME) without pinning a default model. With the macOS Keychain in use, the key is kept out of the config and resolved fromAI_GATEWAY_API_KEY(exported from the shell rc) at runtime instead.2ffbf59: Add Pi support tovercel ai-gateway coding-agents setup. It writes the gateway credential to Pi's nativevercel-ai-gatewayauth entry in~/.pi/agent/auth.json(created0600, honoringPI_CODING_AGENT_DIR) without pinning a default model.bb16ec9:ai-gateway coding-agents setupnow previews before it writes.--dry-runand the pre-apply summary show the planned per-file changes as a masked diff, the resolved key/quota/expiry, and the.bakbackups 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 thenpx skills addinvocation. 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]Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.