@vercel/client
18.12.4 · 18 Nov 2026Apache-2.0119.5k / weekRepositoryHomepagenpmAtom feed
396 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
18.10.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.
Minor Changes
- 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.
18.9.1 – 18.9.33 releases that only update dependencies@vercel/build-utils 15.0.2Show each
- 18.9.323 Oct 2026@vercel/build-utils 15.0.2
- 18.9.222 Oct 2026@vercel/build-utils 15.0.1
- 18.9.122 Oct 2026@vercel/build-utils 15.0.0
18.9.0
20 Oct 2026- 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
- 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.
18.8.6 – 18.8.83 releases that only update dependencies@vercel/build-utils 14.22.0Show each
- 18.8.819 Oct 2026@vercel/build-utils 14.22.0
- 18.8.716 Oct 2026@vercel/build-utils 14.21.3
- 18.8.615 Oct 2026@vercel/build-utils 14.21.2
18.8.5
15 Oct 2026Prevent deployment archives from including ignored files through directory entries.
18.8.2 – 18.8.43 releases that only update dependencies@vercel/build-utils 14.21.1Show each
- 18.8.414 Oct 2026@vercel/build-utils 14.21.1
- 18.8.313 Oct 2026@vercel/build-utils 14.21.0
- 18.8.29 Oct 2026@vercel/build-utils 14.20.1
18.8.1
8 Oct 2026Retry transient upload and deployment status failures, improve network diagnostics, and clarify errors when a deployment outcome cannot be confirmed.
Patch Changes
Retry transient upload and deployment status failures, improve network diagnostics, and clarify errors when a deployment outcome cannot be confirmed.
18.8.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.
Minor Changes
- 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.
18.7.0
5 Oct 2026Flat path
schedulesaccept an optionalrequestMethodofGETorPOST, defaulting toPOST.vercel buildwrites it to Build Output, andvercel devinvokes path schedules with it.Reject prebuilt file references to version-control files before upload while preserving environment-file and dependency references.
Minor Changes
Flat path
schedulesaccept an optionalrequestMethodofGETorPOST, defaulting toPOST.vercel buildwrites it to Build Output, andvercel devinvokes path schedules with it.
Patch Changes
Reject prebuilt file references to version-control files before upload while preserving environment-file and dependency references.
18.6.2
2 Oct 2026Only updates a dependency:@vercel/build-utils 14.17.0
18.6.1
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.
Patch Changes
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.
18.6.0
2 Oct 2026Accept a top-level
daemonsfield invercel.json.vercel devwarns that it doesn't run daemons, andvercel builddoesn't build them yet.
Minor Changes
Accept a top-level
daemonsfield invercel.json.vercel devwarns that it doesn't run daemons, andvercel builddoesn't build them yet.
18.5.0
30 Sep 2026Accept a flat
schedulesformat invercel.jsonthat is aligned withcrons(scheduleplus one ofpath,function,topic, orentrypoint), and emit schedules in the flat format in Build Output APIconfig.json. The nestedexpression/targetformat is still accepted.
Minor Changes
Accept a flat
schedulesformat invercel.jsonthat is aligned withcrons(scheduleplus one ofpath,function,topic, orentrypoint), and emit schedules in the flat format in Build Output APIconfig.json. The nestedexpression/targetformat is still accepted.
18.4.8
29 Sep 2026List up to 100
.vercelignoreviolations needed by prebuilt functions, including each path's effective matching rule and line number, before truncating the deployment warning.
18.4.4 – 18.4.74 releases that only update dependencies@vercel/build-utils 14.13.2Show each
- 18.4.729 Sep 2026@vercel/build-utils 14.13.2
- 18.4.626 Sep 2026@vercel/build-utils 14.13.1
- 18.4.525 Sep 2026@vercel/build-utils 14.13.0
- 18.4.424 Sep 2026@vercel/build-utils 14.12.0
18.4.3
23 Sep 2026Accept runtime-specific schedule entrypoints and provide build plumbing for lowering dedicated entrypoints to function targets. All schedule entrypoints must use one runtime, including for static frameworks and
framework: null. Entrypoints must also match the runtime of frameworks that own one (Next.js, FastAPI, Express). The builder contract still supports multiple entrypoints per function for future runtimes.
Patch Changes
Accept runtime-specific schedule entrypoints and provide build plumbing for lowering dedicated entrypoints to function targets. All schedule entrypoints must use one runtime, including for static frameworks and
framework: null. Entrypoints must also match the runtime of frameworks that own one (Next.js, FastAPI, Express). The builder contract still supports multiple entrypoints per function for future runtimes.
18.4.1 – 18.4.22 releases that only update dependencies@vercel/build-utils 14.10.2@vercel/routing-utils 6.6.0Show each
18.4.0
11 Sep 2026Require schedule jitter to be an integer from 1 to 15 minutes in vercel.json and Build Output API config, matching the maximum SQS message delay. Duration strings are no longer accepted.
Minor Changes
Require schedule jitter to be an integer from 1 to 15 minutes in vercel.json and Build Output API config, matching the maximum SQS message delay. Duration strings are no longer accepted.
Patch Changes
- Security
Bump
@vercel/microfrontendsfrom 1.2.2 to 2.4.0 so@vercel/clientuses patchedpath-to-regexp@6.3.0(GHSA-9wv6-86v2-598j).This is the request-time matcher, unlike the CLI's vendored compile-only copy. 2.x signatures:
findConfigtakescustomConfigFilename, andinferMicrofrontendsLocationtakesapplicationContextinstead ofapplicationName. PassingundefinedforcustomConfigFilenamekeeps the old search formicrofrontends.json/microfrontends.jsonc.
18.3.5
10 Sep 2026Warn on
--prebuiltdeploys when afilePathMapentry is excluded by.vercelignore. An upcoming release will fail closed instead of uploading without those files. Default-ignored dependency directories (node_modules,.next, etc.) are still kept. The CLI records telemetry when a deploy would fail closed.
18.3.4
9 Sep 2026Reduce CLI startup and deployment preparation time through lazy shared dependencies, smaller bundles, parallel Git metadata and file collection, and native executable startup caching. Allow deployment options to resolve asynchronously while the client collects local files.
Keep startup regression tests compatible with asynchronous prompts and Windows Git paths, and allow the NestJS build fixture sufficient time for cold dependency installation.
Patch Changes
Reduce CLI startup and deployment preparation time through lazy shared dependencies, smaller bundles, parallel Git metadata and file collection, and native executable startup caching. Allow deployment options to resolve asynchronously while the client collects local files.
Keep startup regression tests compatible with asynchronous prompts and Windows Git paths, and allow the NestJS build fixture sufficient time for cold dependency installation.
18.3.1 – 18.3.33 releases that only update dependencies@vercel/build-utils 14.9.2Show each
- 18.3.38 Sep 2026@vercel/build-utils 14.9.2
- 18.3.24 Sep 2026@vercel/build-utils 14.9.1
- 18.3.11 Sep 2026@vercel/build-utils 14.9.0
18.3.0
1 Sep 2026Propagate top-level
schedulesfrom vercel.json into the Build Output APIconfig.jsonduringvercel build, and validate the property against the schedules schema
Minor Changes
Propagate top-level
schedulesfrom vercel.json into the Build Output APIconfig.jsonduringvercel build, and validate the property against the schedules schema
18.2.12 – 18.2.228 releases that only update dependencies@vercel/build-utils 14.7.0Show each
- 18.2.2229 Aug 2026@vercel/build-utils 14.7.0
- 18.2.2127 Aug 2026@vercel/build-utils 14.6.1
- 18.2.1926 Aug 2026@vercel/build-utils 14.5.1
- 18.2.1826 Aug 2026@vercel/build-utils 14.5.0
- 18.2.1622 Aug 2026@vercel/build-utils 14.4.0
- 18.2.1521 Aug 2026@vercel/build-utils 14.3.0
- 18.2.1420 Aug 2026@vercel/build-utils 14.2.0
- 18.2.1214 Aug 2026@vercel/build-utils 14.1.1
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.