chore(deps-dev): bump vercel from 54.18.6 to 56.3.2

[dependabot]

Bumps vercel from 54.18.6 to 56.3.2.

Release notes

Sourced from vercel's releases.

vercel@56.3.2

Patch Changes

• 145eb34: Improve vercel ai-gateway coding-agents setup prompts: use the searchable team picker, keep the multiselect key legend visible after the first selection, and narrow the prompt lines by moving context off the question line.

  The apply step now offers a coding-agent handoff: when the key is stored in the macOS Keychain it asks whether to write the files or "Copy a prompt for my agent" (which creates the key, stores it in the Keychain, and copies agent-ready setup instructions — with no plaintext key — to the clipboard); without the Keychain it stays a plain yes/no confirm. A new --apply <edit|prompt> flag drives this non-interactively — --apply prompt writes the prompt to stdout so it can be piped into an agent (… --apply prompt --yes | claude -p), and in machine mode it rides along as a prompt JSON field.

vercel@56.3.1

Patch Changes

• b08b736: Support linked-project deploys with project-scoped tokens that cannot fetch owner user/team resources.

vercel@56.3.0

Minor Changes

• 238543c: Support Python services that declare their web app and development workflow sidecars through a pyproject.toml entrypoint in vercel dev.

Patch Changes

• d5751d6: Allow Env, Target, Flags rules, Routes, Redirects, Firewall, and Git commands to select a project explicitly with --project, including from an unlinked directory.

• 1d8e0ee: Extract project-link validation shared by routes, redirects, and firewall commands.

• b0aa678: Consolidate suggested-command and subcommand-argument helpers while preserving explicit project context and required-argument validation.

• c06b596: Fix vercel domains add sending the alias mutation under a stale ambient team scope. When run inside a directory linked to a project in another team, the command now resolves the local project link (like vercel domains ls) and scopes the domain/alias request to the linked team, so a same-name project in the ambient team can no longer be targeted by mistake.

• a39869e: Fix vercel dev returning 404 for api/ functions using the rust, python, ruby, or go runtimes when the project has a framework dev command (e.g. Next.js). These runtimes are registered by backend framework presets, which caused the dev server to misclassify api/ functions as the frontend build and skip building them.

• a55e7df: Replace user-facing experimentalServices references with services in error/warning messages and rename error codes (NO_EXPERIMENTAL_SERVICES_CONFIGURED → NO_SERVICES_CONFIGURED, MISSING_EXPERIMENTAL_SERVICES → MISSING_SERVICES). The deprecated v1 config key should no longer appear in guidance shown to users.

• e4866e9: Skip the Rust target/ directory by default for Rust projects.

  Rust projects produce a target/ directory of build artifacts that can be hundreds of MB. It's rebuilt on Vercel during the deployment (and cached server-side), so uploading it only slows deployments down. When a root Cargo.toml is detected, target/ is now ignored by default during vercel deploy and vercel dev. Users can opt back in with !/target in their .vercelignore.

  Also hardened the local file scanner used by vercel dev so that a directory removed mid-scan (a common race with cargo build churning target/) is skipped instead of crashing the process.

• 7ea6c7a: Preserve buildCommand and combine preDeployCommand when writing inferred services config to vercel.json in V2 format.

• 4cce813: Write [SENSITIVE] placeholder instead of an empty string when vercel env pull encounters sensitive environment variables whose values cannot be read, so an unset value is distinguishable from a redacted one

• Updated dependencies [b0ed8e5]

• Updated dependencies [c555d3a]

• Updated dependencies [238543c]

• Updated dependencies [f97e2e0]

  • @​vercel/python@​6.51.0
  • @​vercel/build-utils@​13.34.0
  • @​vercel/static-build@​2.11.8
  • @​vercel/backends@​0.8.25
  • @​vercel/container@​0.0.5
  • @​vercel/elysia@​0.1.102

... (truncated)

Changelog

Sourced from vercel's changelog.

56.3.2

Patch Changes

• 145eb34: Improve vercel ai-gateway coding-agents setup prompts: use the searchable team picker, keep the multiselect key legend visible after the first selection, and narrow the prompt lines by moving context off the question line.

  The apply step now offers a coding-agent handoff: when the key is stored in the macOS Keychain it asks whether to write the files or "Copy a prompt for my agent" (which creates the key, stores it in the Keychain, and copies agent-ready setup instructions — with no plaintext key — to the clipboard); without the Keychain it stays a plain yes/no confirm. A new --apply <edit|prompt> flag drives this non-interactively — --apply prompt writes the prompt to stdout so it can be piped into an agent (… --apply prompt --yes | claude -p), and in machine mode it rides along as a prompt JSON field.

56.3.1

Patch Changes

• b08b736: Support linked-project deploys with project-scoped tokens that cannot fetch owner user/team resources.

56.3.0

Minor Changes

• 238543c: Support Python services that declare their web app and development workflow sidecars through a pyproject.toml entrypoint in vercel dev.

Patch Changes

• d5751d6: Allow Env, Target, Flags rules, Routes, Redirects, Firewall, and Git commands to select a project explicitly with --project, including from an unlinked directory.

• 1d8e0ee: Extract project-link validation shared by routes, redirects, and firewall commands.

• b0aa678: Consolidate suggested-command and subcommand-argument helpers while preserving explicit project context and required-argument validation.

• c06b596: Fix vercel domains add sending the alias mutation under a stale ambient team scope. When run inside a directory linked to a project in another team, the command now resolves the local project link (like vercel domains ls) and scopes the domain/alias request to the linked team, so a same-name project in the ambient team can no longer be targeted by mistake.

• a39869e: Fix vercel dev returning 404 for api/ functions using the rust, python, ruby, or go runtimes when the project has a framework dev command (e.g. Next.js). These runtimes are registered by backend framework presets, which caused the dev server to misclassify api/ functions as the frontend build and skip building them.

• a55e7df: Replace user-facing experimentalServices references with services in error/warning messages and rename error codes (NO_EXPERIMENTAL_SERVICES_CONFIGURED → NO_SERVICES_CONFIGURED, MISSING_EXPERIMENTAL_SERVICES → MISSING_SERVICES). The deprecated v1 config key should no longer appear in guidance shown to users.

• e4866e9: Skip the Rust target/ directory by default for Rust projects.

  Rust projects produce a target/ directory of build artifacts that can be hundreds of MB. It's rebuilt on Vercel during the deployment (and cached server-side), so uploading it only slows deployments down. When a root Cargo.toml is detected, target/ is now ignored by default during vercel deploy and vercel dev. Users can opt back in with !/target in their .vercelignore.

  Also hardened the local file scanner used by vercel dev so that a directory removed mid-scan (a common race with cargo build churning target/) is skipped instead of crashing the process.

• 7ea6c7a: Preserve buildCommand and combine preDeployCommand when writing inferred services config to vercel.json in V2 format.

• 4cce813: Write [SENSITIVE] placeholder instead of an empty string when vercel env pull encounters sensitive environment variables whose values cannot be read, so an unset value is distinguishable from a redacted one

• Updated dependencies [b0ed8e5]

• Updated dependencies [c555d3a]

• Updated dependencies [238543c]

• Updated dependencies [f97e2e0]

  • @​vercel/python@​6.51.0
  • @​vercel/build-utils@​13.34.0
  • @​vercel/static-build@​2.11.8

... (truncated)

Commits

• 917f31e Version Packages (#17147)
• 145eb34 [cli] Improve ai-gateway coding-agents setup prompts (#17136)
• e35de4d Version Packages (#17140)
• b08b736 Add support for project-only tokens to vercel deploy (#16999)
• dc224ce Version Packages (#17126)
• d5751d6 feat(cli): add --project support for env, target, flags, routes, redirects, f...
• a55e7df [services] Replace experimentalServices in user-facing messages (#17077)
• 7ea6c7a [services] Preserve buildCommand and preDeployCommand in V2 config infer (#16...
• b0aa678 refactor(cli): consolidate suggested command helpers (#17110)
• 1d8e0ee refactor(cli): extract project link helper (#17109)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[netlify]

✅ Deploy Preview for docs-runme-dev ready!

Name	Link
🔨 Latest commit	bb76df4
🔍 Latest deploy log	https://app.netlify.com/projects/docs-runme-dev/deploys/6a5e00f5f808270008704f46
😎 Deploy Preview	https://deploy-preview-720--docs-runme-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.