chore(deps): bump vercel from 50.44.0 to 55.0.0

[dependabot]

Bumps vercel from 50.44.0 to 55.0.0.

Release notes

Sourced from vercel's releases.

vercel@55.0.0

Major Changes

• 8f10c0b: Require an explicit team signal when linking without a TTY. In non-interactive mode or without a terminal, vercel link (and other commands that set up a link) no longer fall back to the globally selected team from vc switch or the login default, and --yes no longer guesses a team. The team now resolves only from --scope/--team, the scope property in vercel.json, VERCEL_ORG_ID, or a single available team; otherwise the command fails with action_required: missing_scope (JSON in non-interactive mode) before any project discovery runs, before a new project is created, and before the existing .vercel/project.json is deleted. This also removes the slow all-teams project search from non-interactive vercel link runs.
• 8f10c0b: Every command that establishes a link — vercel deploy, vercel pull, vercel dev, vercel git connect, and vercel link itself — now uses the same flow: resolve the team first (explicit --scope/--team, vercel.json scope, VERCEL_ORG_ID, a single available team, or the searchable team picker), then offer project suggestions scoped to that team, preferring projects linked to the local Git repository (which produce a repo-style .vercel/repo.json link) over folder-name matches. The cross-team project sweep and its SSO fallback prompt are removed entirely; project discovery never queries teams other than the one that was resolved. An explicit project name (--project, --name, or vercel.json name) skips the suggestions and resolves directly within the team. An explicit team signal now also skips the team prompt in every command, not just vercel link.
• 8f10c0b: --yes no longer selects a team on its own. It answers confirmations, not data questions: when the account has multiple teams and no explicit signal (--scope/--team, vercel.json scope, VERCEL_ORG_ID), an interactive terminal now asks Which team? once and continues auto-confirmed, instead of silently using the globally selected team from vc switch or the login default. This also removes the all-teams project sweep from vercel link --yes; matches are resolved within the chosen team, and a single Git-linked root-directory match still links automatically.

Minor Changes

• 0922f27: Add vercel integration resource inspect <resource> (alias status) to show a marketplace resource's details and live status fetched fresh from the provider, rather than the cached status shown by vercel integration list. Supports --format=json.
• 8f10c0b: vercel link now honors VERCEL_ORG_ID and VERCEL_PROJECT_ID as an explicit project-owner pair: when both are set, the command resolves and confirms exactly that pair without prompting and without --yes, and leaves local link files untouched. An unresolvable pair errors instead of falling back to prompts. The new-project Name? prompt also suggests a creatable default: when the folder name is already a project in the selected team, it suggests <folder-name>-<short suffix> instead of a name that can only fail "Project already exists" validation.
• 176d939: Add vercel vcr login [engine] to authenticate docker, podman, or buildah with the Vercel Container Registry using an OIDC token.

Patch Changes

... (truncated)

Changelog

Sourced from vercel's changelog.

55.0.0

Major Changes

• 8f10c0b: Require an explicit team signal when linking without a TTY. In non-interactive mode or without a terminal, vercel link (and other commands that set up a link) no longer fall back to the globally selected team from vc switch or the login default, and --yes no longer guesses a team. The team now resolves only from --scope/--team, the scope property in vercel.json, VERCEL_ORG_ID, or a single available team; otherwise the command fails with action_required: missing_scope (JSON in non-interactive mode) before any project discovery runs, before a new project is created, and before the existing .vercel/project.json is deleted. This also removes the slow all-teams project search from non-interactive vercel link runs.
• 8f10c0b: Every command that establishes a link — vercel deploy, vercel pull, vercel dev, vercel git connect, and vercel link itself — now uses the same flow: resolve the team first (explicit --scope/--team, vercel.json scope, VERCEL_ORG_ID, a single available team, or the searchable team picker), then offer project suggestions scoped to that team, preferring projects linked to the local Git repository (which produce a repo-style .vercel/repo.json link) over folder-name matches. The cross-team project sweep and its SSO fallback prompt are removed entirely; project discovery never queries teams other than the one that was resolved. An explicit project name (--project, --name, or vercel.json name) skips the suggestions and resolves directly within the team. An explicit team signal now also skips the team prompt in every command, not just vercel link.
• 8f10c0b: --yes no longer selects a team on its own. It answers confirmations, not data questions: when the account has multiple teams and no explicit signal (--scope/--team, vercel.json scope, VERCEL_ORG_ID), an interactive terminal now asks Which team? once and continues auto-confirmed, instead of silently using the globally selected team from vc switch or the login default. This also removes the all-teams project sweep from vercel link --yes; matches are resolved within the chosen team, and a single Git-linked root-directory match still links automatically.

Minor Changes

• 0922f27: Add vercel integration resource inspect <resource> (alias status) to show a marketplace resource's details and live status fetched fresh from the provider, rather than the cached status shown by vercel integration list. Supports --format=json.
• 8f10c0b: vercel link now honors VERCEL_ORG_ID and VERCEL_PROJECT_ID as an explicit project-owner pair: when both are set, the command resolves and confirms exactly that pair without prompting and without --yes, and leaves local link files untouched. An unresolvable pair errors instead of falling back to prompts. The new-project Name? prompt also suggests a creatable default: when the folder name is already a project in the selected team, it suggests <folder-name>-<short suffix> instead of a name that can only fail "Project already exists" validation.
• 176d939: Add vercel vcr login [engine] to authenticate docker, podman, or buildah with the Vercel Container Registry using an OIDC token.

Patch Changes

... (truncated)

Commits

• 11f0ceb Version Packages (#16947)
• 6b93f07 [CLI] adding multi-phase plan to remove builders (#16980)
• 067a068 [cli] Speed up vercel deploy alias assignment detection (#16986)
• 456d388 [flags] Add support for managing conditional rules (#16909)
• 2522d0a [vercel] add ai-gateway models ls + endpoints commands (#16839)
• 5b29d19 [cli] Fix alert rules flag forwarding (#16968)
• 8f10c0b [CLI] Introducing new VC Link Flow (#16809)
• 7b30856 [python] pyproject.toml subscribers vc dev (#16728)
• 3b98912 Add CLI limit support to paginated lists (#16954)
• d213d27 fix vercel inspect --logs --format json (#16951)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for vercel since your current version.

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
supercli	Ready	Preview, Comment	Jul 10, 2026 12:31pm
supercli-client	Ready	Preview, Comment	Jul 10, 2026 12:31pm
supercli-docs	Ready	Preview, Comment	Jul 10, 2026 12:31pm