@vercel/config
0.15.0 · 18 Nov 2026MIT628k / weekRepositoryHomepagenpmAtom feed
0.15.0 is the newest release of 0.13.x.
Summary· from the note as AI read it
Migration neededRead before upgrading: 1 change to make.
Before you upgrade
- Add a
nameto everyschedulesentry; stop using getScheduleName/defaultScheduleName
Deprecated
- Convert
schedulesarray to an object keyed by schedule name
In short
1 breaking1 deprecated
- Breaking
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.
Release note
The section about @vercel/config 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.
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.