build(deps-dev): bump vercel from 51.4.0 to 52.2.0

[dependabot]

Bumps vercel from 51.4.0 to 52.2.0.

Release notes

Sourced from vercel's releases.

vercel@52.2.0

Minor Changes

• 24686d0: Add configurable auth token storage with keyring-backed persistence and file fallback support.

Patch Changes

• Updated dependencies [24686d0]
• Updated dependencies [d36ee35]
• Updated dependencies [56c9f89]
  • @​vercel/cli-auth@​0.1.0
  • @​vercel/node@​5.7.13

vercel@52.0.0

Major Changes

• fix!: exclude configuration files from static deployments (#16056)

Minor Changes

• Add vercel connex token command to fetch tokens for Connex clients, with auto-authorize / auto-install recovery on actionable 422 errors. (#16072)

Patch Changes

• Add vercel env run example to the env command help output (#16072)

• vercel env update now applies the same Development guards as vercel env add: (#16072)

  • Errors with a docs-linked message when the selected record targets Development and the team has the Sensitive Environment Variables Policy enabled. No PATCH is attempted.
  • Errors when --sensitive is used on a record that targets Development (regardless of policy). Sensitive is not allowed on Development.

  Other env update behavior is unchanged.

• Normalize single-line stdin env values by removing a trailing newline before (#16072) saving them.

• Updated dependencies [2aa78415831fe89d1b21dd89704706bd1ad5e78d, 2aa78415831fe89d1b21dd89704706bd1ad5e78d, 2aa78415831fe89d1b21dd89704706bd1ad5e78d]:

  • @​vercel/build-utils@​13.20.0
  • @​vercel/python@​6.36.0
  • @​vercel/backends@​0.2.0
  • @​vercel/elysia@​0.1.71
  • @​vercel/express@​0.1.81
  • @​vercel/fastify@​0.1.74
  • @​vercel/go@​3.5.0
  • @​vercel/h3@​0.1.80
  • @​vercel/hono@​0.2.74
  • @​vercel/hydrogen@​1.3.6
  • @​vercel/koa@​0.1.54
  • @​vercel/nestjs@​0.2.75
  • @​vercel/next@​4.16.8

... (truncated)

Changelog

Sourced from vercel's changelog.

52.2.0

Minor Changes

• 24686d0: Add configurable auth token storage with keyring-backed persistence and file fallback support.

Patch Changes

• Updated dependencies [24686d0]
• Updated dependencies [d36ee35]
• Updated dependencies [56c9f89]
  • @​vercel/cli-auth@​0.1.0
  • @​vercel/node@​5.7.13

52.1.0

Minor Changes

• ae90f00: vercel edge-config tokens --remove <ID_OR_TOKEN> now accepts either a token id (as shown in the id column of vercel edge-config tokens <id-or-slug>) or a plaintext token string. The CLI transparently consults the store's own token list to classify each value and sends { ids }, { tokens }, or both to DELETE /v1/edge-config/:id/tokens accordingly.

  • Backward compatible: existing scripts passing plaintext tokens keep working.
  • Forward compatible: once plaintext is no longer listed server-side, users can revoke by id with no CLI changes.
  • No new flag: everything stays on --remove, which is repeatable.

  vercel edge-config tokens my-store --remove <token-id> --yes
  vercel edge-config tokens my-store --remove <plaintext-token> --yes
  vercel edge-config tokens my-store --remove <id-1> --remove <plaintext-2> --yes

Patch Changes

• 8d6cfde: Improve CLI unit test portability and argument fixture handling by replacing a POSIX-only mkdir -p call with Node's cross-platform mkdirSync(..., { recursive: true }), and by passing a token fixture as --token=<value> so values beginning with - are parsed correctly in non-interactive token tests.
• 0252860: Prevent non-interactive next.command suggestions from echoing auth tokens across CLI flows, not just tokens add. The CLI now strips --token / -t flags (including inline =value forms) before building suggested rerun commands, so automation output cannot leak credentials copied from invocation args; VERCEL_TOKEN from environment variables was not affected.
• Fail fast on SAML / missing-scope re-authentication when the device-code flow cannot succeed, so commands no longer hang waiting for a browser approval that will never come. reauthenticate now bails with an actionable error message when the token was supplied via --token, when it was supplied via the VERCEL_TOKEN environment variable, or when stdin is non-interactive (e.g. CI). In all three cases the user is told which token source needs a token authorized for the requested scope, instead of silently kicking off performDeviceCodeFlow.
  • @​vercel/static-build@​2.9.21

52.0.0

Major Changes

• fix!: exclude configuration files from static deployments (#16056)

Minor Changes

• Add vercel connex token command to fetch tokens for Connex clients, with auto-authorize / auto-install recovery on actionable 422 errors. (#16072)

Patch Changes

• Add vercel env run example to the env command help output (#16072)

... (truncated)

Commits

• 02c78f5 Version Packages (#16151)
• 68edb7a Version Packages (#16138)
• 24686d0 auth: Make it possible to store CLI credentials in OS keychain (#16083)
• 8d6cfde test(cli): fix windows and non-interactive token unit test regressions (#16134)
• 0252860 fix(cli): prevent token leaks in non-interactive next commands (#16113)
• ae90f00 feat(cli): edge-config tokens --remove accepts ids or plaintext tokens (#16...
• 4eec0e5 Version Packages (#16068)
• 34b7a27 fix!: exclude configuration files from static deployments (#16056)
• 5c9d1b5 [CLI] adding vc env run in help flag (#16044)
• 4d87b5b fix(cli): clean up test projects in env var E2E tests (#16055)
• 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.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
junior-docs	Ready	Preview, Comment	May 7, 2026 2:48am

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.