Packages

@vercel/build-utils

15.5.0 · 18 Nov 2026Apache-2.07.9M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/build-utils From 13.14.1 to 13.36.3

43 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 13.14.1Latest15.5.0
  1. 13.14.1yours
  2. 36 releases
  3. 13.33.1breaking
  4. 5 releases
  5. 13.36.3target

Before you upgrade

Tick each one off as you go
  • Breaking13.33.1

Release by release

  1. 13.36.3

    30 Jul 20262 fixes
    • Fixed

      Propagate per-function maxConcurrency configuration into build outputs and keep every configured Next.js route in its own Lambda group, including routes with the same limit.

    • Fixed

      Type shared function settings in container image build outputs.

  2. 13.36.2

    29 Jul 20261 fix
    • Fixed

      Preserve 4-byte UTF-8 characters when streaming string FileBlob contents (fixes Edge Function corruption during vercel build).

  3. 13.36.1

    29 Jul 20266 new
    • New

      [[tool.vercel.subscribers]] entrypoints are introspected at build time via vercel.queue.get_subscriptions() and served through generated vercel.queue.asgi_app() handler modules, with queue/v2beta triggers carrying the SDK-registered consumer groups and per-subscription tuning.

    • New

      Celery and Dramatiq projects get the matching vercel-celery/vercel-dramatiq integration package injected automatically (bundled variant unless vercel-queue is an explicit dependency), in builds and in vercel dev.

    • New

      [[tool.vercel.workflows]] entrypoints follow the SDK generation: projects on vercel >= 0.8.0 are served through vercel-queue like subscribers; older or undeterminable versions keep the legacy vercel-workers serving (worker env markers, injected pinned vercel-workers).

    • New

      Projects that depend on vercel-workers directly keep the legacy integration wholesale: legacy subscriber schema, direct entrypoint serving, worker env markers.

    • New

      vercel dev serves queue sidecars through vercel.queue.asgi_app() for new-SDK projects, and its queue broker delivers with the SDK-registered consumer groups introspected at sidecar startup (matching production trigger behavior); legacy projects keep the vercel-workers bootstrap.

    • New

      The CLI no longer injects config.hasWorkerServices; the Python builder makes all queue-serving decisions from project metadata.

  4. 13.36.0

    27 Jul 20261 new
    • New

      Support Node.js Routing Middleware entrypoints through proxy.entrypoint, with optional path matching through proxy.matcher. The matcher may be configured in the entrypoint source or vercel.json, but not both.

  5. 13.35.0

    24 Jul 20261 new
    • New

      Make service bindings type optional.

  6. 13.34.0

    16 Jul 20261 new
    • New

      Support Python services that declare their web app and development workflow sidecars through a pyproject.toml entrypoint in vercel dev.

  7. 13.33.1

    Migration needed15 Jul 20261 fix
    • Breaking

      BREAKING CHANGE (@vercel/client): the agent?: http.Agent option was replaced with dispatcher?: FetchDispatcher (an undici dispatcher, e.g.

    • Fixed

      Migrate @vercel/client and @vercel/build-utils from node-fetch to native fetch. This removes the last url.parse() usage from the CLI bundle, which triggered a DEP0169 DeprecationWarning on Node 24 (visible in the standalone binary during vercel deploy).

  8. 13.33.0

    13 Jul 20261 new
    • New

      Add service information to deploy-manifest.

1 other line we could not sort, mostly version bumps
  • Revert "[flags] fix dep detection for build embedding (#16242)"

    13.26.5

2 internal lines (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.