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

[dependabot]

Bumps vercel from 52.2.0 to 54.18.6.

Release notes

Sourced from vercel's releases.

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

• 0eea3d6: Expose cacheReason in vc logs output, alongside the existing cache status, so users can see why a request was a cache MISS/BYPASS/STALE.
  • @​vercel/static-build@​2.11.4

vercel@54.18.4

Patch Changes

• 16cf8f6: Surface the builds rate-limit upgrade hint on vercel deploy. The hint previously never printed (the error was dropped before conversion) and pointed at the CLI self-updater; it now renders the backend's plan-appropriate call to action (ctaLabel/ctaUrl, or legacy action/link) from the error, falling back to a plan-agnostic nudge.
• 56875d2: Remove the non-functional vercel buy v0 subcommand; use vercel buy credits v0 to purchase v0 credits.
• 6c5aa14: Support lazily generated Build Output services configs during vc build.

vercel@54.18.3

Patch Changes

• 262e935: Fixed vercel dev for the container framework when used as a top-level build (outside of services).

  • The dev server now maps the container preset's <detect> sentinel to a discovered Dockerfile (Dockerfile.vercel, Containerfile.vercel, Dockerfile, or Containerfile), so the build is recognized instead of warning that it "did not match any source files".
  • The @vercel/container build() path no longer throws `vercel dev` cannot build container images from a Dockerfile during dev. Containers are always built from a Dockerfile/Containerfile (there is no prebuilt-image input); in dev the image is built and run locally by startDevServer, so build() returns a stable local tag without pushing to a registry.
  • The dev server no longer treats a container build output (an OCI image reference, runtime: "container") as a zip-based function. It previously failed with output.createZip is not a function while trying to spin the image up under fun; container outputs are now skipped there and served by the builder's startDevServer instead.
  • The dev path (startDevServer) now discovers the Dockerfile.vercel / Containerfile.vercel opt-in markers when the container entrypoint is the <detect> sentinel, matching the build path. Previously it only looked for a bare Dockerfile, so a project using a .vercel marker failed with "Container service must specify an entrypoint…" even though deploys worked. The discovery helper is now shared between the build and dev paths.
  • vercel dev now fails fast with a clear message when the Docker daemon isn't running ("Could not connect to the Docker daemon. Start Docker…") instead of a cryptic Container "undefined" exited (code 125) before becoming ready.. Container start failures also now name the actual container and include the underlying Docker error output.
  • The container dev server is now reused across requests. Previously the image was rebuilt and a fresh container started on every HTTP request (the result was missing the persistent flag); now a live container is kept and reused for the same service, matching how other persistent builders behave.

• 9e3f9cd: [services] service name validation

• 9e3f9cd: Align services and experimentalServicesV2 service-name validation with the platform schema.

• Updated dependencies [262e935]

• Updated dependencies [e05ed3c]

  • @​vercel/container@​0.0.4
  • @​vercel/next@​4.20.2
  • @​vercel/static-build@​2.11.4

vercel@54.18.2

Patch Changes

• 1a1c745: [services] fix bare static service builds, allow services with only 'root' to resolve at @​vercel/static
  • @​vercel/static-build@​2.11.4

vercel@54.18.1

Patch Changes

... (truncated)

Changelog

Sourced from vercel's changelog.

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

54.18.5

Patch Changes

• 0eea3d6: Expose cacheReason in vc logs output, alongside the existing cache status, so users can see why a request was a cache MISS/BYPASS/STALE.
  • @​vercel/static-build@​2.11.4

54.18.4

Patch Changes

• 16cf8f6: Surface the builds rate-limit upgrade hint on vercel deploy. The hint previously never printed (the error was dropped before conversion) and pointed at the CLI self-updater; it now renders the backend's plan-appropriate call to action (ctaLabel/ctaUrl, or legacy action/link) from the error, falling back to a plan-agnostic nudge.
• 56875d2: Remove the non-functional vercel buy v0 subcommand; use vercel buy credits v0 to purchase v0 credits.
• 6c5aa14: Support lazily generated Build Output services configs during vc build.

54.18.3

Patch Changes

• 262e935: Fixed vercel dev for the container framework when used as a top-level build (outside of services).

  • The dev server now maps the container preset's <detect> sentinel to a discovered Dockerfile (Dockerfile.vercel, Containerfile.vercel, Dockerfile, or Containerfile), so the build is recognized instead of warning that it "did not match any source files".
  • The @vercel/container build() path no longer throws `vercel dev` cannot build container images from a Dockerfile during dev. Containers are always built from a Dockerfile/Containerfile (there is no prebuilt-image input); in dev the image is built and run locally by startDevServer, so build() returns a stable local tag without pushing to a registry.
  • The dev server no longer treats a container build output (an OCI image reference, runtime: "container") as a zip-based function. It previously failed with output.createZip is not a function while trying to spin the image up under fun; container outputs are now skipped there and served by the builder's startDevServer instead.
  • The dev path (startDevServer) now discovers the Dockerfile.vercel / Containerfile.vercel opt-in markers when the container entrypoint is the <detect> sentinel, matching the build path. Previously it only looked for a bare Dockerfile, so a project using a .vercel marker failed with "Container service must specify an entrypoint…" even though deploys worked. The discovery helper is now shared between the build and dev paths.
  • vercel dev now fails fast with a clear message when the Docker daemon isn't running ("Could not connect to the Docker daemon. Start Docker…") instead of a cryptic Container "undefined" exited (code 125) before becoming ready.. Container start failures also now name the actual container and include the underlying Docker error output.
  • The container dev server is now reused across requests. Previously the image was rebuilt and a fresh container started on every HTTP request (the result was missing the persistent flag); now a live container is kept and reused for the same service, matching how other persistent builders behave.

• 9e3f9cd: [services] service name validation

• 9e3f9cd: Align services and experimentalServicesV2 service-name validation with the platform schema.

• Updated dependencies [262e935]

• Updated dependencies [e05ed3c]

  • @​vercel/container@​0.0.4
  • @​vercel/next@​4.20.2
  • @​vercel/static-build@​2.11.4

54.18.2

Patch Changes

• 1a1c745: [services] fix bare static service builds, allow services with only 'root' to resolve at @​vercel/static

... (truncated)

Commits

• 6c80539 Version Packages (#16871)
• e833330 fix(cli): point rolling-release start at dedicated start endpoint (#16868)
• 9b579db Version Packages (#16857)
• 0eea3d6 Expose cacheReason in vc logs output (#16767)
• 52bc240 Version Packages (#16846)
• 6c5aa14 Support generated stable services config (#16847)
• ea136cb [cli] Add copywriting guidance (#16774)
• 56875d2 [cli] Remove the non-functional vercel buy v0 subcommand (#16694)
• 16cf8f6 [cli] Surface the builds rate-limit upgrade hint and fix its target (#16693)
• b58e9f5 Version Packages (#16840)
• Additional commits viewable in compare view

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
vega-editor-backend	Ready	Preview, Comment	Jul 1, 2026 5:08am