@vercel/config
0.15.0 · 18 Nov 2026MIT628k / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/config From 0.12.0 to 0.15.0
4 releases in betweennotes for 2
Reading releases, release notes and advisories…
- 2+
- changes to make
- 0
- advisories fixed
- 1+
- new
- ?
- fixes
Counted from 2 of 4 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking0.14.0
- Deprecated0.13.0
Release by release
0.14.1 – 0.15.02 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.
- 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.
- Deprecated
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.