Make Vercel CLI 55 project linking safe for CI agents
Vercel CLI 55 changes how vercel link, deploy, pull, dev, and git connect resolve teams and projects. CI and agent workflows should pass --team/--scope or set VERCELORGID and VERCELPROJECTID before upgrading, because --yes no longer select...
What you get from it
Vercel CLI 55 changes how vercel link, deploy, pull, dev, and git connect resolve teams and projects. CI and agent workflows should pass --team/--scope or set VERCELORGID and VERCELPROJECTID before upgrading, because --yes no longer selects a team automatically.
Use this as an upgrade checkpoint before moving CI, coding agents, or deployment scripts to Vercel CLI 55. The linking flow now resolves the team first and searches projects inside that team, which makes project discovery faster but removes an old implicit behavior: --yes confirms prompts, but it does not choose a team.
For promptless runs, set VERCEL_ORG_ID and VERCEL_PROJECT_ID, or pass --team/--scope explicitly. If a command has multiple possible teams and no explicit signal, non-interactive runs can fail with action_required: missing_scope before creating or touching a link. That is useful for safety, but only if your automation expects it.
Discussion
Share practical experience, questions, or warnings with the community.
Sign in to join the discussion and vote on comments.
Sign in