chore(paddle)(deps-dev): bump vercel from 54.18.2 to 54.20.1 in /paddle-webhook

[dependabot]

Bumps vercel from 54.18.2 to 54.20.1.

Release notes

Sourced from vercel's releases.

vercel@54.20.1

Patch Changes

• 4b1306c: List vercel agent-runs in the root CLI help output.
• 0b64f51: Add missing commands to the root vercel --help list: ai-gateway, edge-config, oauth-apps, sandbox, and tokens

vercel@54.20.0

Minor Changes

• b9e4f06: Add a vercel agent-runs command for Agent Runs observability: list lists Agent Runs for a project, inspect <runId> shows run metadata, events, usage, and subagents, trace <runId> shows the full trace (turns, messages, reasoning, and tool calls), and projects lists projects in the team with Agent Runs activity. All subcommands support --json for machine-readable output.

vercel@54.19.0

Minor Changes

• 2c87793: Add vercel vcr commands to manage Vercel Container Registry repositories and images.

Patch Changes

• 84c01ff: Add install as an alias for vercel integration add.
• 08d234f: Merge routes from generated Build Output config with builder routes when nesting Services V2 output, so framework routes and generated service or custom routes are all preserved.
• 6e004b1: Accept all marketplace integration legal documents (addendum, privacy policy, terms of service) with a single confirmation instead of one prompt each. The links are now listed together, each on its own line, before asking.

vercel@54.18.7

Patch Changes

• 4d9394b: Bridge WebSocket close to response close

• c4667d3: Fix vc build run from a monorepo subdirectory (gated behind VERCEL_RESOLVE_ROOT_DIRECTORY=1).

  When a project is linked in place (apps/api/.vercel/project.json) and vc build is run from that directory, the build previously treated the linked subdirectory as the repository root. Because the project's dependencies are typically hoisted to the monorepo root above it, this broke builds in several ways that share one root cause:

  • A rootDirectory setting that restates the link's own location (e.g. apps/api for a link at apps/api) double-appended into apps/api/apps/api, failing with ENOENT … /apps/api/apps/api/.next/package.json.
  • With --standalone, the package-manager symlink that makes a dependency resolvable (apps/api/node_modules/hono → ../../node_modules/.pnpm/.../hono) was skipped because its target pointed outside the subdirectory, so the deployed function failed at runtime with Cannot find module 'hono' even though the dependency's files were packaged.
  • Builders traced from the wrong root, so Next.js set an incorrect outputFileTracingRoot/turbopack.root (Turbopack errors; Webpack .nft.json omits hoisted dependencies).

  With the flag enabled, a per-directory link is resolved like a repository-level link: the repository root is detected (workspace markers, then git) and the project is expressed as its path relative to that root, so the build is anchored correctly regardless of which directory the command is run from. The rootDirectory setting is interpreted relative to the link's location and honored when it points at a folder that exists; otherwise (e.g. the redundant apps/api/apps/api case) it is ignored in favor of the link's own location and a warning is emitted. Standalone builds additionally preserve the package-manager symlinks (rather than skipping them) so dependencies resolve at runtime. Behavior is unchanged when the flag is not set.

• Updated dependencies [69892ba]

  • @​vercel/rust@​1.4.0
  • @​vercel/node@​5.8.22

vercel@54.18.6

Patch Changes

• e833330: Point rolling release start at the dedicated rolling-release start API endpoint.
• Updated dependencies [cbf22bf]
  • @​vercel/backends@​0.8.21
  • @​vercel/express@​0.1.112

vercel@54.18.5

Patch Changes

... (truncated)

Changelog

Sourced from vercel's changelog.

54.20.1

Patch Changes

• 4b1306c: List vercel agent-runs in the root CLI help output.
• 0b64f51: Add missing commands to the root vercel --help list: ai-gateway, edge-config, oauth-apps, sandbox, and tokens

54.20.0

Minor Changes

• b9e4f06: Add a vercel agent-runs command for Agent Runs observability: list lists Agent Runs for a project, inspect <runId> shows run metadata, events, usage, and subagents, trace <runId> shows the full trace (turns, messages, reasoning, and tool calls), and projects lists projects in the team with Agent Runs activity. All subcommands support --json for machine-readable output.

54.19.0

Minor Changes

• 2c87793: Add vercel vcr commands to manage Vercel Container Registry repositories and images.

Patch Changes

• 84c01ff: Add install as an alias for vercel integration add.
• 08d234f: Merge routes from generated Build Output config with builder routes when nesting Services V2 output, so framework routes and generated service or custom routes are all preserved.
• 6e004b1: Accept all marketplace integration legal documents (addendum, privacy policy, terms of service) with a single confirmation instead of one prompt each. The links are now listed together, each on its own line, before asking.

54.18.7

Patch Changes

• 4d9394b: Bridge WebSocket close to response close

• c4667d3: Fix vc build run from a monorepo subdirectory (gated behind VERCEL_RESOLVE_ROOT_DIRECTORY=1).

  When a project is linked in place (apps/api/.vercel/project.json) and vc build is run from that directory, the build previously treated the linked subdirectory as the repository root. Because the project's dependencies are typically hoisted to the monorepo root above it, this broke builds in several ways that share one root cause:

  • A rootDirectory setting that restates the link's own location (e.g. apps/api for a link at apps/api) double-appended into apps/api/apps/api, failing with ENOENT … /apps/api/apps/api/.next/package.json.
  • With --standalone, the package-manager symlink that makes a dependency resolvable (apps/api/node_modules/hono → ../../node_modules/.pnpm/.../hono) was skipped because its target pointed outside the subdirectory, so the deployed function failed at runtime with Cannot find module 'hono' even though the dependency's files were packaged.
  • Builders traced from the wrong root, so Next.js set an incorrect outputFileTracingRoot/turbopack.root (Turbopack errors; Webpack .nft.json omits hoisted dependencies).

  With the flag enabled, a per-directory link is resolved like a repository-level link: the repository root is detected (workspace markers, then git) and the project is expressed as its path relative to that root, so the build is anchored correctly regardless of which directory the command is run from. The rootDirectory setting is interpreted relative to the link's location and honored when it points at a folder that exists; otherwise (e.g. the redundant apps/api/apps/api case) it is ignored in favor of the link's own location and a warning is emitted. Standalone builds additionally preserve the package-manager symlinks (rather than skipping them) so dependencies resolve at runtime. Behavior is unchanged when the flag is not set.

• Updated dependencies [69892ba]

  • @​vercel/rust@​1.4.0
  • @​vercel/node@​5.8.22

54.18.6

Patch Changes

• e833330: Point rolling release start at the dedicated rolling-release start API endpoint.
• Updated dependencies [cbf22bf]

... (truncated)

Commits

• e40839d Version Packages (#16919)
• 0b64f51 [CLI] fixing all help commands in general list (#16918)
• 4b1306c Add agent-runs to root CLI help (#16917)
• 9d8e28e Version Packages (#16906)
• b9e4f06 [CLI] Adding agent runs in the CLI (#16904)
• 0d7ddb1 Version Packages (#16893)
• 08d234f Merge generated output routes with build routes (#16889)
• 2c87793 feat(packages/cli): support VCR command (#16883)
• 84c01ff add install as a subcommand (#16891)
• 6e004b1 Accept marketplace integration terms with a single confirmation (#16890)
• 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 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)

[dependabot]

Labels

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

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