@vercel/build-utils
15.5.0 · 18 Nov 2026Apache-2.07.9M / weekRepositoryHomepagenpmAtom feed
345 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 15.x · latest line
15.1.0
27 Oct 2026Summary· from the note as AI read it
Read before upgrading: 1 change to make.
- Breaking
Remove the deprecated array format for
schedules.schedulesinvercel.json, in Build Outputconfig.json, and fromgetDevManifestmust be an object keyed by schedule name.@vercel/configno longer exportsSchedule(useScheduleDefinition), and@vercel/clientno longer exportsVercelConfigSchedule.
Minor Changes
Add an experimental Buildah image store cache, enabled with
VERCEL_BUILDAH_STORE_CACHE=1, so builds reuse images and layers from earlier deployments. Concurrent service builds share one--source-date-epochper deployment so their layers stay reusable.@vercel/build-utilsnow exportsresolveBuildConcurrency().- Breaking
Remove the deprecated array format for
schedules.schedulesinvercel.json, in Build Outputconfig.json, and fromgetDevManifestmust be an object keyed by schedule name.@vercel/configno longer exportsSchedule(useScheduleDefinition), and@vercel/clientno longer exportsVercelConfigSchedule.
15.0.2
23 Oct 2026Report the runtime preset for services without a framework.
15.0.1
22 Oct 2026Support
livenessProbeinvercel.json#daemons.
15.0.0
22 Oct 2026Summary· from the note as AI read it
Read before upgrading: 2 changes to make.
- Breaking
Remove the legacy BYOC extension's build-output collection and deserialization utilities, Lambda finalization and size validation, and serverless environment/streaming helpers. BYOC function preparation now uses
vercel deploy describe.The removed exports include
deserializeBuildOutput,deserializeLambda,deserializeEdgeFunction,finalizeLambda,collectUncompressedSize, thevalidateBuildResultandvalidateLambdaSizefamilies,getEncryptedEnv,getLambdaEnvironment,getLambdaPreloadScripts,getLambdaSupportsStreaming, and the associated collection/deserialization and serverless types. Also remove the unused standalonemd5helper. PreservestreamToDigestAsync,sha256,FileDigest, andExtendedBodyData, which still have build-container consumers.Remove the Node builder's outdated reference to the shared streaming helper; its AWS custom-handler streaming behavior is unchanged.
Major Changes
- Breaking
Remove the legacy BYOC extension's build-output collection and deserialization utilities, Lambda finalization and size validation, and serverless environment/streaming helpers. BYOC function preparation now uses
vercel deploy describe.The removed exports include
deserializeBuildOutput,deserializeLambda,deserializeEdgeFunction,finalizeLambda,collectUncompressedSize, thevalidateBuildResultandvalidateLambdaSizefamilies,getEncryptedEnv,getLambdaEnvironment,getLambdaPreloadScripts,getLambdaSupportsStreaming, and the associated collection/deserialization and serverless types. Also remove the unused standalonemd5helper. PreservestreamToDigestAsync,sha256,FileDigest, andExtendedBodyData, which still have build-container consumers.Remove the Node builder's outdated reference to the shared streaming helper; its AWS custom-handler streaming behavior is unchanged.
Minor Changes
Allow explicitly selecting Node.js 26 for local builds without an environment variable.
Patch Changes
Accept a command argument array and
rootwith Dockerfile and Containerfile schedule entrypoints. This adds configuration support; building and executing these schedules will follow separately.
- 14.x
14.23.0
20 Oct 2026- Deprecated
schedulesinvercel.jsoncan now be an object keyed by schedule name, like"schedules": { "nightly": { "schedule": "0 0 * * *", "path": "/api/cron" } }.vercel buildwritesschedulesto Build Outputconfig.jsonin the format it was given, and builders can return it fromgetDevManifest. The array of named schedules still works but is deprecated, andvercel buildandvercel devwarn when it's used. Require
nameforschedulesentries invercel.jsonand Build Outputconfig.json. Schedules without anameno longer get a derived default name, andgetScheduleNameanddefaultScheduleNameare removed from@vercel/build-utils.Accept service bindings on daemons in
vercel.json.
Minor Changes
Require
nameforschedulesentries invercel.jsonand Build Outputconfig.json. Schedules without anameno longer get a derived default name, andgetScheduleNameanddefaultScheduleNameare removed from@vercel/build-utils.- Deprecated
schedulesinvercel.jsoncan now be an object keyed by schedule name, like"schedules": { "nightly": { "schedule": "0 0 * * *", "path": "/api/cron" } }.vercel buildwritesschedulesto Build Outputconfig.jsonin the format it was given, and builders can return it fromgetDevManifest. The array of named schedules still works but is deprecated, andvercel buildandvercel devwarn when it's used.
Patch Changes
Accept service bindings on daemons in
vercel.json.Fix
ENOENTbuild failures when daemons are deployed alongside a zero-config server app that has nopublic/directory.
14.22.0
19 Oct 2026Add
functions[glob].installCommand. For matching@vercel/nodefunctions, an empty string skips the dependency install and a non-empty value runs instead of the default install. Builds warn when the property matches functions of other runtimes, which ignore it.Use Vercel Flags project activation metadata to detect when to embed flag definitions, including builds without installed SDK packages. Preserve explicit embedding overrides and existing SDK detection for projects without activation metadata.
14.21.3
16 Oct 2026Display the edge middleware deprecation warning in yellow with a bold WARNING! prefix during builds and at
vercel devstartup. Add an optional builder hook for detecting startup warnings without starting a development server.
14.21.2
15 Oct 2026Add opt-in support for Node.js 26.
14.21.1
14 Oct 2026Detect Yarn 4 from lockfile versions 9 and 10 (written by Yarn 4.14+), so workspace-scoped installs and the Yarn 3/4
enableGlobalCachesetup apply to newer Yarn 4 projects.
14.21.0
13 Oct 2026- Deprecated
Accept
instancesfor daemons invercel.json.replicasis deprecated and ignored wheninstancesis set. Daemon build output now writesinstances. Support
terminationGracePeriodSecondsinvercel.json#daemons.
14.20.1
9 Oct 2026Parse
yarn.lockwith js-yamlsafeLoadso custom JS tags like!!js/functionare rejected
14.20.0
8 Oct 2026Add an optional
serviceto function-targetschedules, naming the service that ownsfunction.functionis then the path within that service.vercel devdoes not run service-hosted schedule targets yet.
14.19.0
6 Oct 2026- Breaking
Breaking (beta): the nested
expression/targetschedulesformat is no longer supported invercel.jsonor Build Output.schedulesentries usescheduleplus exactly one ofpath,function,topic, orentrypoint, with optionalname,timezone, andjitter. Whennameis omitted, it defaults to a hash of the target and cron expression, matching the name the API derives.vercel buildleaves unnamed schedules unnamed inconfig.json, except entrypoint schedules, which keep the derived name their function dispatches on.Schedulenow has the flat shape. Removed exports:parseScheduleDefinition,formatBuildOutputSchedule,FlatBuildOutputSchedule,ScheduleExpression, andScheduleTargetfrom@vercel/build-utils;FlatScheduleDefinition,LegacyScheduleDefinition, andScheduleDefinitionfrom@vercel/config; andVercelConfigFlatSchedulefrom@vercel/client.
14.18.0
5 Oct 2026Flat path
schedulesaccept an optionalrequestMethodofGETorPOST, defaulting toPOST.vercel buildwrites it to Build Output, andvercel devinvokes path schedules with it.Move static file copying to build utils.
Add an experimental workspace-scoped install path for Node builds to avoid installing unrelated monorepo workspaces.
14.17.0
2 Oct 2026Build top-level
daemonswhenVERCEL_ENABLE_DAEMONS_BOA=1:vercel buildbuilds the project as usual, pushes each daemon's Dockerfile image, and writes a Build Output API descriptor todaemons/<name>/.vc-config.json.Prevent static deployments from accidentally publishing daemon source files. Both static builders skip nested daemon roots with a warning and reject publishing a directory that is itself a daemon root. Build scripts can still deliberately publish files through a separate output directory.
14.16.0
2 Oct 2026Make
nameoptional for flatschedulesentries. When omitted, the name defaults to a hash of the target and cron expression, matching the name the API derives.vercel buildleaves unnamed schedules unnamed inconfig.json, except entrypoint schedules, which keep the derived name their function dispatches on.
14.15.0
2 Oct 2026Accept a top-level
daemonsfield invercel.json.vercel devwarns that it doesn't run daemons, andvercel builddoesn't build them yet.
14.14.0
30 Sep 2026Accept a flat
schedulesformat invercel.jsonthat is aligned withcrons(scheduleplus one ofpath,function,topic, orentrypoint), and emit schedules in the flat format in Build Output APIconfig.json. The nestedexpression/targetformat is still accepted.
14.13.2
29 Sep 2026Allow projects to temporarily extend Node.js 20 support through November 1, 2026.
14.13.1
26 Sep 2026Build Python schedule entrypoints. A
.pyentrypoint such asjobs/nightly.pyruns as a script once per firing in a private function under_vercel/schedules/. Entrypoints with the samefunctionsconfig share one function, which runs the script for the dispatched schedule name, so the project's dependencies are bundled once per distinct config instead of once per script. Entrypoints withoutfunctionsconfig share_vercel/schedules/default; the others' function is named after thefunctionspatterns their config came from, such as_vercel/schedules/jobs/report. Schedule names must be unique within a shared function.Declared schedule entrypoints are not served as static files, but other files follow the normal static rules. When a project with Python schedule entrypoints publishes other
.pyfiles from its root, through the zero-config static fallback oroutputDirectory: ".",vercel buildnow warns and lists them.Add
findMatchingFunctionto@vercel/build-utils, which returns thefunctionsentry that applies to a function.
14.13.0
25 Sep 2026Support
afterCacheBypassrules in Build Output APIconfig.json, preserving request and cached response header conditions through builds and deserialization.
14.12.0
24 Sep 2026Add
onMisstoPrerender.onMiss?: 'sync' | 'dynamic';
Declares how a request is served when no prerendered output is available for it yet. Absent means
sync: block the response on rendering it.dynamicserves the request dynamically while the static shell is regenerated in the background. The value is carried unvalidated so an unknown mode cannot fail a deploy.
14.11.0
23 Sep 2026Define an optional builder-owned development manifest for function identities, local invocation targets, trigger metadata, and native schedule definitions. Conventional functions can use host-owned per-entrypoint discovery; frameworks can override it. The host retains ownership of processes, readiness, and registration reconciliation.
Accept runtime-specific schedule entrypoints and provide build plumbing for lowering dedicated entrypoints to function targets. All schedule entrypoints must use one runtime, including for static frameworks and
framework: null. Entrypoints must also match the runtime of frameworks that own one (Next.js, FastAPI, Express). The builder contract still supports multiple entrypoints per function for future runtimes.
14.10.2
22 Sep 2026- Removed
Remove
payloadfrom static schedule configuration invercel.json. Static schedules no longer accept or expose a payload field; use dynamic schedules for payload support.
14.10.1
14 Sep 2026Add experimental Cloud Native Buildpacks lifecycle support with isolated source staging, pinned lifecycle and buildpack archives, and runtime-owned image resolution. Ruby images are selected from
.ruby-version,.tool-versions, or thetools.rubyentry inmise.toml, then an exact Gemfile declaration, defaulting to Ruby 3.4. Unsupported version declarations fail with configuration guidance. Nothing selects a buildpack yet.Fix
bun installsilently discardingbun.lockfiles withlockfileVersion: 2(written by Bun >= 1.4). The install step now selects the Bun 1.4 binary whenever the lockfile requires it, mirroring how the pnpm version is already inferred from its lockfile version, instead of always running the container's default Bun 1.3.x install.Fix native CLI build/dev worker dispatch, preserve the system Node executable for shell commands, resolve project analytics versions outside the binary snapshot, pair dynamically installed builders with compatible build-utils versions, and lazily materialize the packaged esbuild executable for JavaScript and TypeScript configuration files.
Patch Changes
Add experimental Cloud Native Buildpacks lifecycle support with isolated source staging, pinned lifecycle and buildpack archives, and runtime-owned image resolution. Ruby images are selected from
.ruby-version,.tool-versions, or thetools.rubyentry inmise.toml, then an exact Gemfile declaration, defaulting to Ruby 3.4. Unsupported version declarations fail with configuration guidance. Nothing selects a buildpack yet.Fix
bun installsilently discardingbun.lockfiles withlockfileVersion: 2(written by Bun >= 1.4). The install step now selects the Bun 1.4 binary whenever the lockfile requires it, mirroring how the pnpm version is already inferred from its lockfile version, instead of always running the container's default Bun 1.3.x install.Fix native CLI build/dev worker dispatch, preserve the system Node executable for shell commands, resolve project analytics versions outside the binary snapshot, pair dynamically installed builders with compatible build-utils versions, and lazily materialize the packaged esbuild executable for JavaScript and TypeScript configuration files.
Require maxConcurrency to be an integer from 1 to 8192.
14.10.0
11 Sep 2026Require schedule jitter to be an integer from 1 to 15 minutes in vercel.json and Build Output API config, matching the maximum SQS message delay. Duration strings are no longer accepted.
Add an optional IANA
timezoneto schedules invercel.jsonand Build Output API config. Omitted timezones use UTC. Validate configured timezones before building.More robust Next.js framework version detection
14.9.3
9 Sep 2026Reduce CLI startup and deployment preparation time through lazy shared dependencies, smaller bundles, parallel Git metadata and file collection, and native executable startup caching. Allow deployment options to resolve asynchronously while the client collects local files.
Keep startup regression tests compatible with asynchronous prompts and Windows Git paths, and allow the NestJS build fixture sufficient time for cold dependency installation.
14.9.2
8 Sep 2026Raise the client-side
maxDurationvalidation limit to 3600 seconds.
14.9.1
4 Sep 2026Delay the pnpm 11 created-at default so unpinned lockfile 9.0 projects stay on pnpm 10. pnpm 11's default
minimumReleaseAgeof 1 day was breaking installs of freshly published packages. ExplicitpackageManager/devEnginespins to pnpm 11 are unchanged.
14.9.0
1 Sep 2026Honor pnpm 12 pins without auto-adopting, and stop passing
--unsafe-permtopnpm install.When Corepack is off, a lockfile-compatible
packageManager/devEngines.packageManager/engines.pnpmpin for 12.x selects/pnpm12if that directory exists. Unpinned lockfile9.0still defaults to pnpm 9/10/11 by project creation date.pnpm installno longer includes--unsafe-perm, which pnpm 12's Rust CLI rejects.
14.8.0
1 Sep 2026Propagate top-level
schedulesfrom vercel.json into the Build Output APIconfig.jsonduringvercel build, and validate the property against the schedules schema
14.7.0
29 Aug 2026Add build type to deploy manifest.
Accept
schedule/v1betatriggers in theLambdaruntime validation and the functions config schema
14.6.1
27 Aug 2026Run on-disk JavaScript workers with a lazily resolved system Node.js executable in native CLI installations, and install the matching Build Utils preview tarball for dynamically installed Builders.
14.5.1
26 Aug 2026Revert dependency install log rewriting that piped pnpm stdout through an unread Transform and could hang large installs.
14.5.0
26 Aug 2026Expose the resolved rewrite destination as the request path observed by Node backend framework applications (express, hono, h3, koa, nestjs, fastify, elysia) and the unified backends builder, and warn affected backend projects about the behavior change.
14.4.0
22 Aug 2026Replace
prerenderClassificationonPrerenderwithinitialMetadata.The platform consumes only the request-time compute mode and the HTML shell size, so the flattened four-field taxonomy (
routeType,response,compute,htmlSize) is reduced to a single grouped field:initialMetadata?: { compute: 'blocking' | 'resuming' | 'static'; htmlSize?: number; }The group is named
initialMetadatabecause the values describe the deployment as it was built: revalidation can regenerate a route's output over the deployment's lifetime, so readers must treat them as initial values, not live state.@vercel/nextreadscomputeandhtmlSizeoff the v4 prerender-manifest taxonomy and deliberately ignoresrouteTypeandresponse; the values are still carried unvalidated so a compute mode added by a future framework release cannot hard-fail a deploy, and they are still set only on the primary output of each prerender group.htmlSize: 0is a real size (a shell that postponed everything);htmlSizeis absent when there is no HTML shell to measure (route handlers, Pages Router). Absence of the whole group remains legitimate (notFoundRoutes, Pages Routerfallback: false, older frameworks).
14.3.0
21 Aug 2026Honor
package.jsonpnpm pins without Corepack, and default new projects to pnpm 11.When Corepack is off,
devEngines.packageManageris preferred, then a lockfile-compatiblepackageManagerfield, thenengines.pnpmas a selector. Unpinned lockfile9.0projects created on or after 2026-08-19 use pnpm 11 (Node 22+) if/pnpm11is present in the build image; otherwise they keep pnpm 10.Canonicalized internal service contract ownership.
Simplify dependency installation logs to show the selected package manager and version.
14.2.0
20 Aug 2026Add schedules/v1beta to TriggerEvent types
14.1.1
14 Aug 2026Support selecting Bun 1.4.x as an explicit runtime and build-time package manager, including local Bun servers.
14.1.0
13 Aug 2026Move middleware matcher utils from node builder to general build utils.
14.0.5
11 Aug 2026Remove redundant and ineffective package tests.
Patch Changes
Remove redundant and ineffective package tests.
14.0.4
10 Aug 2026Support pnpm lockfiles containing multiple YAML documents.
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.