@vercel/build-utils
15.5.0 · 18 Nov 2026Apache-2.07.9M / weekRepositoryHomepagenpmAtom feed
In short
1 deprecated1 new2 fixed
- 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.
Release note
The section about @vercel/build-utils of a note shared by several packages.
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.
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.