@vercel/build-utils
15.5.0 · 18 Nov 2026Apache-2.07.9M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/build-utils From 8.4.2 to 15.5.0
200 releases in betweennotes for 192
Reading releases, release notes and advisories…
- 23+
- changes to make
- 0
- advisories fixed
- 162+
- new
- 131+
- fixes
Counted from 192 of 200 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking15.1.0
- Breaking15.0.0
- Breaking14.19.0
- Breaking14.10.2
- Breaking13.33.1
- Breaking13.2.11
- Breaking13.2.11
- Breaking13.2.11
- Breaking13.2.11
- Breaking13.2.11
Release by release
15.1.1 – 15.5.08 releases, no release note
- 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. - New
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
- Fixed
Report the runtime preset for services without a framework.
- Fixed
- New
Support
livenessProbeinvercel.json#daemons.
- New
- 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. - New
Allow explicitly selecting Node.js 26 for local builds without an environment variable.
- Fixed
Accept a command argument array and
rootwith Dockerfile and Containerfile schedule entrypoints. This adds configuration support; building and executing these schedules will follow separately.
- Breaking
- 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. - New
Require
nameforschedulesentries invercel.jsonand Build Outputconfig.json. Schedules without anameno longer get a derived default name, andgetScheduleNameanddefaultScheduleNameare removed from@vercel/build-utils. - Fixed
Accept service bindings on daemons in
vercel.json. - Fixed
Fix
ENOENTbuild failures when daemons are deployed alongside a zero-config server app that has nopublic/directory.
- Deprecated
- New
Add
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. - Fixed
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.
- New
- Fixed
Display 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.
- Fixed
13 other lines we could not sort, mostly version bumps
- 13.26.5
Revert "[flags] fix dep detection for build embedding (#16242)"
- 13.4.3
Consolidate
workspaceandentrypointfromexperimentalServicesvercel.jsonschema - 13.4.3
Make
frameworkconfig in service optional -- infer framework from service workspace when not explicitly provided - 13.2.11
Revert "Remove getSpawnOptions"
- 13.2.11
Revert "[build-utils] Fix corepack
packageManagerdetection on monorepos" - 13.2.11
Revert "Revert "Revert "Fix corepack
packageManagerdetection on monorepos""" - 13.2.11
Revert "Revert "Fix corepack
packageManagerdetection on monorepos"" - 13.2.11
Revert "Revert "warn on mismatched corepack and detected package managers""
- 13.2.11
Revert "warn on mismatched corepack and detected package managers"
- 13.2.11
Revert "Fix corepack
packageManagerdetection on monorepos"
20 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.