@vercel/config
0.15.0 · 18 Nov 2026MIT628k / weekRepositoryHomepagenpmAtom feed
57 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 0.15.x · latest line
0.15.0
18 Nov 2026- 0.14.x
0.14.1
28 Oct 20260.14.0
27 Oct 2026Summary· from the note as AI read it
Read before upgrading: 1 change to make.
- 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.
- 0.13.x
0.13.0
20 Oct 2026Summary· from the note as AI read it
Read before upgrading: 1 change to make.
- 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.
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.
- 0.12.x
0.12.0
8 Oct 2026Add 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.
- 0.11.x
0.11.0
6 Oct 2026- 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.Schedulenow has the flat shape. Removed exports:parseScheduleDefinition,formatBuildOutputSchedule,FlatBuildOutputSchedule,ScheduleExpression, andScheduleTargetfrom@vercel/build-utils;FlatScheduleDefinition,LegacyScheduleDefinition, andScheduleDefinitionfrom@vercel/config; andVercelConfigFlatSchedulefrom@vercel/client.
- 0.10.x
0.10.0
5 Oct 2026Flat path
schedulesaccept an optionalrequestMethodofGETorPOST, defaulting toPOST.vercel buildwrites it to Build Output, andvercel devinvokes path schedules with it.
- 0.9.x
0.9.0
2 Oct 2026Make
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.
- 0.8.x
0.8.0
2 Oct 2026Accept the flat
schedulesformat (scheduleplus one ofpath,function,topic, orentrypoint) inVercelConfig, and exportFlatScheduleDefinition,LegacyScheduleDefinition, andScheduleDefinitiontypes. The nestedexpression/targetformat is still accepted.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.
- 0.7.x
0.7.2
23 Sep 2026Add
schedulesandschedule/v1betafunction triggers to the generatedvercel.tsconfig types.
0.7.1
14 Sep 2026Only updates a dependency:@vercel/routing-utils 6.6.0
0.7.0
27 Aug 2026Add strict function affinity configuration and serialize it into function outputs.
- 0.6.x
0.6.1
13 Aug 2026Only updates a dependency:@vercel/routing-utils 6.5.0
0.6.0
13 Aug 2026Add
maxConcurrencyto the per-function configuration type.
- 0.5.x
0.5.6
3 Aug 2026Bump all workspace packages to trigger a full publish from vercel-internal.
Patch Changes
Bump all workspace packages to trigger a full publish from vercel-internal.
0.5.5
25 Jun 2026Only updates a dependency:@vercel/routing-utils 6.4.0
0.5.4
23 Jun 2026Support
request.pathtransforms on routes and high-level rewrites, lowering path-to-regexp parameters such as/:path*to low-level capture references such as/$1
[config] support request path transforms in the router builder
[cli] preserve request path transform syntax and environment metadata across AI/manual route edits
Patch Changes
Support
request.pathtransforms on routes and high-level rewrites, lowering path-to-regexp parameters such as/:path*to low-level capture references such as/$1
[config] support request path transforms in the router builder
[cli] preserve request path transform syntax and environment metadata across AI/manual route edits
0.5.2 – 0.5.32 releases with no change for you1 dependency update, 1 maintenance@vercel/routing-utils 6.3.0Show each
- 0.5.317 Jun 2026docs, tests or tooling
- 0.5.210 Jun 2026@vercel/routing-utils 6.3.0
0.5.1
28 May 2026Drop top-level
envsupport for the newservice-refshape for services.
0.5.0
15 May 2026Add preDeployCommand for experimentalServices
- 0.4.x
0.4.0
13 May 2026Add support for env vars injection that reference other services in
serviceswith an explicitenvconfiguration.
- 0.3.x
0.3.0
30 Apr 2026Upgrade to TypeScript 5.9
Minor Changes
Upgrade to TypeScript 5.9
- 0.2.x
0.2.1
17 Apr 2026Add new job service type support
0.2.0
15 Apr 2026Add root to experimentalServices to set a service's working directory.
- 0.1.x
0.1.1
11 Apr 2026Add
mountsupport for experimental services across config validation and service resolution.
0.1.0
24 Mar 2026Support multiple topics for a single worker service
Support for specifying an env prefix for each service
Minor Changes
Support multiple topics for a single worker service
Support for specifying an env prefix for each service
- 0.0.x
0.0.41
21 Mar 2026Only updates a dependency:@vercel/routing-utils 6.1.0
0.0.40
17 Mar 2026Fix rewrite() and redirect() return types for VercelConfig compatibility
0.0.39
10 Mar 2026Adds support for subdomai configuration in experimentalServices
0.0.38
9 Mar 2026Fix type generation
0.0.35 – 0.0.373 releases that only update dependencies@vercel/routing-utils 6.0.2Show each
- 0.0.373 Mar 2026@vercel/routing-utils 6.0.2
- 0.0.3627 Feb 2026@vercel/routing-utils 6.0.1
- 0.0.3526 Feb 2026@vercel/routing-utils 6.0.0
0.0.33
19 Feb 2026Fix rewrite regexp conversion when header transforms are present
0.0.32
19 Feb 2026Add a new
matchersexport that exposes helpers to make matching against headers, query params, cookies, and host simpler to write.
0.0.31
17 Feb 2026Add support for
functions[*].functionFailoverRegionsinvercel.jsonand build output config generation.This enables per-function failover region configuration instead of only top-level defaults for all functions.
0.0.30
12 Feb 2026Add new expirementalTrigger format for queues v2beta
0.0.29
10 Feb 2026Add support for
regionsinvercel.jsonfunction-level configuration.Matching function
regionsare now parsed fromfunctionsconfig, written into lambda output config, and documented in config types so they override top-level deployment regions for that function.
0.0.28
26 Jan 2026Add maxConcurrency to experimentalTriggers
0.0.27
26 Jan 2026- Removed
Remove references to nonexistent
redirectsproperty
0.0.26
21 Jan 2026Add
experimentalServicestovercel.json
0.0.25
5 Jan 2026Update to support respectOriginCacheControl
0.0.24
16 Dec 2025Update to public
0.0.23
12 Dec 2025Support env in routes, rewrites, and redirects
0.0.22
2 Dec 2025Update env callback
0.0.21
1 Dec 2025Update to routes, via a singleton
0.0.20
21 Nov 2025Full parity in types
0.0.19
20 Nov 2025Test overhaul
0.0.18
20 Nov 2025Update rewrites deprecation
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.