chore(deps-dev): bump vercel from 53.1.1 to 53.2.0 in the github-actions group

[dependabot]

Bumps the github-actions group with 1 update: vercel.

Updates vercel from 53.1.1 to 53.2.0

Release notes

Sourced from vercel's releases.

vercel@53.2.0

Minor Changes

• 3898acb: Add vercel firewall command for managing project firewall configuration. Supports custom rules (add, edit, delete, enable, disable, reorder), IP blocking, system bypass rules, attack challenge mode, and system mitigations.

Patch Changes

• 0cf132c: vercel connex create now accepts a --triggers flag. When passed, the request body includes triggers: { enabled: true } so the server wires webhook triggers into the created client. Without the flag, triggers: { enabled: false } is sent.
• 1d766af: Let --yes enable the browser recovery flow for vercel connex token even in non-TTY contexts (e.g., coding agents), so a single command can open the browser, poll, and return the token without round-tripping through the agent's chat.
• dd27e25: Added vercel deploy continue --error to mark manual deployments as failed with an optional error message.
• 2f2b3f1: Added --filter/-f <NAME> flag to vercel project ls for filtering projects by name (substring match).
• b2c2541: Avoid resolving the configured default team before unscoped vercel link --yes --project cross-team search, so team-scoped tokens can still link projects they can access.
• 5f3cf99: Skip SAML-protected ("limited") teams during vercel link's cross-team auto-detect so it no longer forces device-code re-authentication for scopes the user did not explicitly choose. The project is still linked from any accessible team where it's found, and limited scopes remain available through the standard scope picker (selectOrg) or --scope <slug>.
  • @​vercel/python@​6.38.0

Changelog

Sourced from vercel's changelog.

53.2.0

Minor Changes

• 3898acb: Add vercel firewall command for managing project firewall configuration. Supports custom rules (add, edit, delete, enable, disable, reorder), IP blocking, system bypass rules, attack challenge mode, and system mitigations.

Patch Changes

• 0cf132c: vercel connex create now accepts a --triggers flag. When passed, the request body includes triggers: { enabled: true } so the server wires webhook triggers into the created client. Without the flag, triggers: { enabled: false } is sent.
• 1d766af: Let --yes enable the browser recovery flow for vercel connex token even in non-TTY contexts (e.g., coding agents), so a single command can open the browser, poll, and return the token without round-tripping through the agent's chat.
• dd27e25: Added vercel deploy continue --error to mark manual deployments as failed with an optional error message.
• 2f2b3f1: Added --filter/-f <NAME> flag to vercel project ls for filtering projects by name (substring match).
• b2c2541: Avoid resolving the configured default team before unscoped vercel link --yes --project cross-team search, so team-scoped tokens can still link projects they can access.
• 5f3cf99: Skip SAML-protected ("limited") teams during vercel link's cross-team auto-detect so it no longer forces device-code re-authentication for scopes the user did not explicitly choose. The project is still linked from any accessible team where it's found, and limited scopes remain available through the standard scope picker (selectOrg) or --scope <slug>.
  • @​vercel/python@​6.38.0

Commits

• 23540b5 Version Packages (#16226)
• b2c2541 fix(cli): avoid default scope lookup during link (#16231)
• 5f3cf99 Skip limited teams during vercel link auto detect (#16220)
• 7fc11eb ci: remove redundant build step and fix VITEST_WORKER_ID (#16229)
• 3f0e9b7 Revert "ci: improve E2E log ergonomics in GitHub Actions" (#16225)
• 9bf71cc ci: improve E2E log ergonomics in GitHub Actions
• dd27e25 [cli] Allow continuing a deployment to error (#16203)
• da93fcc Replace Jest with Vitest across workspace tests (#16215)
• 0cf132c feat(cli): add --triggers to connex create behind FF_CONNEX_TRIGGERS (#16102)
• c6b49e4 [ci] Shard vercel CLI unit tests into 7 chunks via VITEST_TEST_FILES (#16208)
• Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
openresource-dev	Ready	Preview, Comment	May 7, 2026 7:26am