Faster, predictable project linking in the Vercel CLI
The Vercel CLI v55 improves project linking by resolving your team first and searching projects only within that team instead of all teams. This makes linking faster and more predictable. Breaking changes include requiring explicit team selection in scripts that previously relied on --yes or global team settings.
The now resolves your team before discovering projects, then searches for projects only in that team instead of sweeping every team you belong to. Linking is faster and more predictable, and every command that establishes a link (, , , , and ) follows the same flow:Vercel CLIvercel linkdeploypulldevgit connect
For CI and agent workflows, setting and makes fully promptless, while or settles the team on any command. When more than one team is available and no signal is set, non-interactive commands fail with an error (JSON output) before they create anything or touch an existing link.VERCEL_ORG_IDVERCEL_PROJECT_IDvercel link--team--scopeaction_required: missing_scope
If a script relied on or your globally selected team to pick where a project links, pass the team explicitly:Vercel CLI 55 is a major version bump and includes breaking changes.--yes
See the for the full list of changes.vercel@55.0.0 release notes
Update the Vercel CLI to v55.0.0 or later with to get started. Learn more about .npm i -g vercel@latestproject linking
Teams resolve from an explicit signal (such as , , the field in , or ), if you only have one team, or from a searchable picker.
--team--scopescopevercel.jsonVERCEL_ORG_IDProject suggestions begin with projects already linked to your local Git repository, then fall back to an exact folder-name match before opening up search and project creation across the team.
The flag answers confirmations without ever selecting a team for you.
--yes
Source: original entry ↗