Packages

@vercel/build-utils

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

Upgrading @vercel/build-utils From 13.32.1 to 13.32.2

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 13.32.1Newest 13.x13.36.3Latest15.5.0
  1. 13.32.1yours
  2. 13.32.2target
0
changes to make
0
advisories fixed
0
new
1
fix

Release by release

  1. 13.32.2

    27 Jun 20261 fix
    • Fixed

      Apply per-service functions config when building experimental V2 services. Previously, function configuration declared under services.<name>.functions in vercel.json (experimentalTriggers, maxDuration, memory, architecture, regions, functionFailoverRegions, supportsCancellation) was dropped at build time — only the top-level functions map was honored. The build now feeds each service's functions to its lambdas for both single-lambda builders (@vercel/node, etc., via writeBuildResultV3) and framework builders that read config.functions (e.g. @vercel/next, via the builder config). Derived queue/v2beta consumer groups are now scoped by the owning service name so two services that declare the same function path + topic no longer collide.

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.