build(deps): Bump vercel from 51.7.0 to 51.8.0

[dependabot]

Bumps vercel from 51.7.0 to 51.8.0.

Release notes

Sourced from vercel's releases.

vercel@51.8.0

Minor Changes

• vercel env add now defaults Environment Variables to sensitive on Production and Preview. Sensitive values are encrypted at rest and cannot be retrieved later via the dashboard or CLI; they are still resolved for builds, deployments, vercel env pull, and runtime. (#16041)

  Behavior per target:

  • Production or Preview: defaults to sensitive. Pass --no-sensitive to opt back in to the previous encrypted behavior (value remains readable later).
  • Development: always stored as encrypted (sensitive is not supported by the Vercel API for Development). Passing --sensitive alongside a Development target now errors up-front instead of silently falling back.
  • Mixed selection (e.g., interactive checkbox picks production + preview + development): errors and asks you to run vercel env add separately for Development, because Development cannot share a record type with Production/Preview.

  Flag summary:

  • --sensitive: unchanged in meaning (request a sensitive variable); now errors when combined with Development.
  • --no-sensitive: new; opt out of the new default for Production/Preview.
  • --sensitive --no-sensitive together: errors.

  On teams that enable the "Enforce Sensitive Environment Variables" policy in team settings, the CLI now reads the policy from the team object and notes in the output that the policy is active; the server already promotes Production/Preview variables to sensitive silently, and the CLI's own logs are now honest about it. Passing --no-sensitive on a policy-on team for Production/Preview now emits a warning — the flag is a no-op because the server promotes the variable regardless — and the CLI sends type: 'sensitive' so its own --debug output matches what gets stored.

Patch Changes

• Updated dependencies [c1866cf1add2107f91cae8292e38e4854bfe0aca]:
  • @​vercel/build-utils@​13.19.1
  • @​vercel/backends@​0.1.2
  • @​vercel/elysia@​0.1.70
  • @​vercel/express@​0.1.80
  • @​vercel/fastify@​0.1.73
  • @​vercel/go@​3.5.0
  • @​vercel/h3@​0.1.79
  • @​vercel/hono@​0.2.73
  • @​vercel/hydrogen@​1.3.6
  • @​vercel/koa@​0.1.53
  • @​vercel/nestjs@​0.2.74
  • @​vercel/next@​4.16.8
  • @​vercel/node@​5.7.12
  • @​vercel/python@​6.35.0
  • @​vercel/redwood@​2.4.12
  • @​vercel/remix-builder@​5.7.2
  • @​vercel/ruby@​2.3.2
  • @​vercel/rust@​1.1.1
  • @​vercel/static-build@​2.9.20

Changelog

Sourced from vercel's changelog.

51.8.0

Minor Changes

• vercel env add now defaults Environment Variables to sensitive on Production and Preview. Sensitive values are encrypted at rest and cannot be retrieved later via the dashboard or CLI; they are still resolved for builds, deployments, vercel env pull, and runtime. (#16041)

  Behavior per target:

  • Production or Preview: defaults to sensitive. Pass --no-sensitive to opt back in to the previous encrypted behavior (value remains readable later).
  • Development: always stored as encrypted (sensitive is not supported by the Vercel API for Development). Passing --sensitive alongside a Development target now errors up-front instead of silently falling back.
  • Mixed selection (e.g., interactive checkbox picks production + preview + development): errors and asks you to run vercel env add separately for Development, because Development cannot share a record type with Production/Preview.

  Flag summary:

  • --sensitive: unchanged in meaning (request a sensitive variable); now errors when combined with Development.
  • --no-sensitive: new; opt out of the new default for Production/Preview.
  • --sensitive --no-sensitive together: errors.

  On teams that enable the "Enforce Sensitive Environment Variables" policy in team settings, the CLI now reads the policy from the team object and notes in the output that the policy is active; the server already promotes Production/Preview variables to sensitive silently, and the CLI's own logs are now honest about it. Passing --no-sensitive on a policy-on team for Production/Preview now emits a warning — the flag is a no-op because the server promotes the variable regardless — and the CLI sends type: 'sensitive' so its own --debug output matches what gets stored.

Patch Changes

• Updated dependencies [c1866cf1add2107f91cae8292e38e4854bfe0aca]:
  • @​vercel/build-utils@​13.19.1
  • @​vercel/backends@​0.1.2
  • @​vercel/elysia@​0.1.70
  • @​vercel/express@​0.1.80
  • @​vercel/fastify@​0.1.73
  • @​vercel/go@​3.5.0
  • @​vercel/h3@​0.1.79
  • @​vercel/hono@​0.2.73
  • @​vercel/hydrogen@​1.3.6
  • @​vercel/koa@​0.1.53
  • @​vercel/nestjs@​0.2.74
  • @​vercel/next@​4.16.8
  • @​vercel/node@​5.7.12
  • @​vercel/python@​6.35.0
  • @​vercel/redwood@​2.4.12
  • @​vercel/remix-builder@​5.7.2
  • @​vercel/ruby@​2.3.2
  • @​vercel/rust@​1.1.1
  • @​vercel/static-build@​2.9.20

Commits

• 670553a Version Packages (#16046)
• 193c515 feat(cli): env add sensitive by default for Production and Preview (#16041)
• See full diff in compare view

Maintainer changes

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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)