@vercel/config
0.15.0 · 18 Nov 2026MIT628k / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/config From 0.4.0 to 0.15.0
21 releases in betweennotes for 19
Reading releases, release notes and advisories…
- 3+
- changes to make
- 0
- advisories fixed
- 11+
- new
- 2+
- fixes
Counted from 19 of 21 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking0.14.0
- Breaking0.11.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
- New
Add 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.
- New
- 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.
- Breaking
- New
Flat path
schedulesaccept an optionalrequestMethodofGETorPOST, defaulting toPOST.vercel buildwrites it to Build Output, andvercel devinvokes path schedules with it.
- New
- New
Make
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.
- New
- New
Accept the flat
schedulesformat (scheduleplus one ofpath,function,topic, orentrypoint) inVercelConfig, and exportFlatScheduleDefinition,LegacyScheduleDefinition, andScheduleDefinitiontypes. The nestedexpression/targetformat is still accepted. - New
Add the optional
skipMiddlewareRequestBodyboolean toVercelConfig, matching thevercel.jsonschema. When enabled, routing middleware omits the request body while the destination request body is preserved. Defaults to false.
- New
7 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.