Credentials storage now configurable; connector terminology standardized

Minor Changes

• fddeb55: Add configurable credentials storage handling across the CLI auth stack. Storage of credentials can be configured by the new credStorage key in global config.json or the new VERCEL_TOKEN_STORAGE environment variable. The environment variable takes precedence over the configuration key. Accepted values are file (store credentials in auth.json), keyring (store credentials in system keyring, e.g macOS Keychain or Secrets Service on Linux), and auto (try storing in keyring if available, fall back to file if keyring is not available).

  @vercel/oidc supports keyring-stored authentication credentials by delegating the OIDC minting to the CLI executable via @vercel/cli-exec.

Patch Changes

• a869874: [connect] Rename user-facing "client" references to "connector"

  Updates the vercel connect CLI commands to use the official "connector" terminology in all user-facing surfaces: help text argument names (remove/attach/detach), usage strings in error messages, and the --format=json output key (clients → connectors) for vercel connect list.

• 200aa3b: [connect] Forward --scopes and --installation-id into the authorize/install recovery URL

  When vercel connect token hits an action-required error (user_authorization_required or client_installation_required), the CLI builds an authorize/install URL for the user to complete consent in the browser. Previously this URL carried only teamId and request_code, dropping the --scopes and --installation-id the user supplied. As a result the consent flow fell back to provider defaults (e.g. Slack's users.profile:read), and the post-authorization token retry mismatched the requested scopes. The CLI now forwards scopes (comma-joined) and installationId as query params, which the authorize and install endpoints already accept.

• 3019788: [services] Remove the services field from vercel.json and the VERCEL_USE_SERVICES gate.

• fe893ec: [services] Add experimentalServicesV2 field to vercel.json implementing the new schema for services.

• d22d812: [cli] Nest integration-resource under integration resource and add integration resource connect

  The marketplace resource subcommands (disconnect, remove, create-threshold) are now discoverable under vercel integration resource <sub>. The standalone vercel integration-resource and vc ir forms still work as hidden aliases — no scripts or tests break.

  Adds a new vercel integration resource connect <resource> [project] command (the inverse of disconnect). Accepts --environment (repeatable, defaults to all three), --prefix for env var namespacing, --yes, and --format=json. Defaults to the project linked in the current directory when <project> is omitted.

  Tightens disconnect to error (exit 1) when the specified project is not connected to the resource, instead of exiting 0 with a "not found" message.

  Both commands emit a structured outputAgentError payload with reason: confirmation_required and a next: [{command}] retry hint when run in non-interactive / agent mode without --yes. When connect fails because an env var with the same name already exists on the target project, the error names the conflicting variable and suggests --prefix or vercel env rm as remediation.

• Updated dependencies [3019788]

• Updated dependencies [fe893ec]

• Updated dependencies [fddeb55]

  • @vercel/build-utils@13.26.6
  • @vercel/cli-auth@0.3.0
  • @vercel/cli-config@0.2.0
  • @vercel/backends@0.8.5
  • @vercel/elysia@0.1.86
  • @vercel/express@0.1.96
  • @vercel/fastify@0.1.89
  • @vercel/go@3.8.0
  • @vercel/h3@0.1.95
  • @vercel/hono@0.2.89
  • @vercel/hydrogen@1.3.8
  • @vercel/koa@0.1.69
  • @vercel/nestjs@0.2.90
  • @vercel/next@4.17.5
  • @vercel/node@5.8.10
  • @vercel/python@6.44.0
  • @vercel/redwood@2.4.15
  • @vercel/remix-builder@5.8.6
  • @vercel/ruby@2.4.0
  • @vercel/rust@1.3.0
  • @vercel/static-build@2.9.35