NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #4794 most downloaded on npm
Latest stable
15.3.0
Last release 16 days ago
05 Nov 2026
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
511 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
e29c83e: Container services and daemons can build one stage of a multi-stage Dockerfile by naming it after # in entrypoint, like Dockerfile#worker (do
e29c83e: Container services and daemons can build one stage of a multi-stage Dockerfile by naming it after # in entrypoint, like Dockerfile#worker (docker build --target worker), so several of them can share one Dockerfile. Command schedules accept the same entrypoint form.
e9320e2: Accept the keyless method rule in experimentalBypassFor.
experimentalBypassFor: [{ type: 'method', value: 'POST' }];
Like host, a method rule matches its value against the request itself and
takes no key. The proxy already honors it, which lets Next.js replace the
next-action / content-type header pair it emits for Server Actions with a
single method rule. PrerenderExperimentalBypassFor extends the existing bypass
rules with method matching while route HasField conditions stay unchanged.
Method rules must define a value; omitted or undefined values are rejected.
root, using existing schedule triggers and Build Output API targets. The service root is the schedule image's build context. Reject top-level functions keys that name a command schedule's Dockerfile, and exclude service files from unused-function matching. Keep command schedule sources out of static output like daemon sources, through a new servicesContext build meta field. createStaticPublishFilter replaces createDaemonStaticFileFilter and reads both fields from meta. Reject schedule roots and Dockerfiles that resolve outside the project.VERCEL_ALLOW_DISCONTINUED_NODEJS20 escape hatch.server/ when a static service publishes ., and warns which service roots were skipped. Publishing a directory that is another service's root fails the build with INVALID_SERVICE_ROOT, asking to set outputDirectory.Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
8e49a01: Record each build's workspace in deploy-manifest.json.
Nothing published for this version
cd2647b: Use Node.js 26 by default and for matching broad engine ranges without an environment variable.
Nothing published for this version
Nothing published for this version
11a7991: Record service and daemon counts, build concurrency, and per-build timing totals on the vc.doBuild span, and the service name, runtime, and k
vc.doBuild span, and the service name, runtime, and kind on each service or daemon vc.builder span. Spans now expose their duration once stopped.d0629bd: Remove the deprecated array format for schedules. schedules in vercel.json, in Build Output config.json, and from getDevManifest must be an o…
VERCEL_BUILDAH_STORE_CACHE=1, so builds reuse images and layers from earlier deployments. Concurrent service builds share one --source-date-epoch per deployment so their layers stay reusable. @vercel/build-utils now exports resolveBuildConcurrency().schedules. schedules in vercel.json, in Build Output config.json, and from getDevManifest must be an object keyed by schedule name. @vercel/config no longer exports Schedule (use ScheduleDefinition), and @vercel/client no longer exports VercelConfigSchedule.2f0edaf: Report the runtime preset for services without a framework.
1a379a3: Support livenessProbe in vercel.json#daemons.
livenessProbe in vercel.json#daemons.fec2df1: Remove the legacy BYOC extension's build-output collection and deserialization utilities, Lambda finalization and size validation, and server
fec2df1: Remove the legacy BYOC extension's build-output collection and deserialization utilities, Lambda finalization and size validation, and serverless environment/streaming helpers. BYOC function preparation now uses vercel deploy describe.
The removed exports include deserializeBuildOutput, deserializeLambda, deserializeEdgeFunction, finalizeLambda, collectUncompressedSize, the validateBuildResult and validateLambdaSize families, getEncryptedEnv, getLambdaEnvironment, getLambdaPreloadScripts, getLambdaSupportsStreaming, and the associated collection/deserialization and serverless types. Also remove the unused standalone md5 helper. Preserve streamToDigestAsync, sha256, FileDigest, and ExtendedBodyData, which still have build-container consumers.
Remove the Node builder's outdated reference to the shared streaming helper; its AWS custom-handler streaming behavior is unchanged.
root with Dockerfile and Containerfile schedule entrypoints. This adds configuration support; building and executing these schedules will follow separately.The array of named schedules still works but is deprecated, and vercel build and vercel dev warn when it's used.
name for schedules entries in vercel.json and Build Output config.json. Schedules without a name no longer get a derived default name, and getScheduleName and defaultScheduleName are removed from @vercel/build-utils.schedules in vercel.json can now be an object keyed by schedule name, like "schedules": { "nightly": { "schedule": "0 0 * * *", "path": "/api/cron" } }. vercel build writes schedules to Build Output config.json in the format it was given, and builders can return it from getDevManifest. The array of named schedules still works but is deprecated, and vercel build and vercel dev warn when it's used.vercel.json.ENOENT build failures when daemons are deployed alongside a zero-config server app that has no public/ directory.a2e9f5d: Add functions[glob].installCommand. For matching @vercel/node functions, an empty string skips the dependency install and a non-empty value r
functions[glob].installCommand. For matching @vercel/node functions, an empty string skips the dependency install and a non-empty value runs instead of the default install. Builds warn when the property matches functions of other runtimes, which ignore it.bb42e81: Display the edge middleware deprecation warning in yellow with a bold WARNING! prefix during builds and at vercel dev startup. Add an optiona…
vercel dev startup. Add an optional builder hook for detecting startup warnings without starting a development server.cd68435: Add opt-in support for Node.js 26.
1336097: Detect Yarn 4 from lockfile versions 9 and 10 (written by Yarn 4.14+), so workspace-scoped installs and the Yarn 3/4 enableGlobalCache setup
enableGlobalCache setup apply to newer Yarn 4 projects.24a7e04: Accept instances for daemons in vercel.json. replicas is deprecated and ignored when instances is set. Daemon build output now writes instanc…
instances for daemons in vercel.json. replicas is deprecated and ignored when instances is set. Daemon build output now writes instances.terminationGracePeriodSeconds in vercel.json#daemons.42cc083: Parse yarn.lock with js-yaml safeLoad so custom JS tags like !!js/function are rejected
yarn.lock with js-yaml safeLoad so custom JS tags like !!js/function are rejectede041037: Add an optional service to function-target schedules, naming the service that owns function. function is then the path within that service. v
service to function-target schedules, naming the service that owns function. function is then the path within that service. vercel dev does not run service-hosted schedule targets yet.e58b37a: Breaking (beta): the nested expression/target schedules format is no longer supported in vercel.json or Build Output. schedules entries use s
e58b37a: Breaking (beta): the nested expression/target schedules format is no longer supported in vercel.json or Build Output. schedules entries use schedule plus exactly one of path, function, topic, or entrypoint, with optional name, timezone, and jitter. When name is omitted, it defaults to a hash of the target and cron expression, matching the name the API derives. vercel build leaves unnamed schedules unnamed in config.json, except entrypoint schedules, which keep the derived name their function dispatches on.
Schedule now has the flat shape. Removed exports: parseScheduleDefinition, formatBuildOutputSchedule, FlatBuildOutputSchedule, ScheduleExpression, and ScheduleTarget from @vercel/build-utils; FlatScheduleDefinition, LegacyScheduleDefinition, and ScheduleDefinition from @vercel/config; and VercelConfigFlatSchedule from @vercel/client.
94f6cea: Flat path schedules accept an optional requestMethod of GET or POST, defaulting to POST. vercel build writes it to Build Output, and vercel d
schedules accept an optional requestMethod of GET or POST, defaulting to POST. vercel build writes it to Build Output, and vercel dev invokes path schedules with it.28a7ab7: Build top-level daemons when VERCEL_ENABLE_DAEMONS_BOA=1: vercel build builds the project as usual, pushes each daemon's Dockerfile image, an
daemons when VERCEL_ENABLE_DAEMONS_BOA=1: vercel build builds the project as usual, pushes each daemon's Dockerfile image, and writes a Build Output API descriptor to daemons/<name>/.vc-config.json.20c5940: Make name optional for flat schedules entries. When omitted, the name defaults to a hash of the target and cron expression, matching the name
name optional for flat schedules entries. When omitted, the name defaults to a hash of the target and cron expression, matching the name the API derives. vercel build leaves unnamed schedules unnamed in config.json, except entrypoint schedules, which keep the derived name their function dispatches on.a7ef28c: Accept a top-level daemons field in vercel.json. vercel dev warns that it doesn't run daemons, and vercel build doesn't build them yet.
daemons field in vercel.json. vercel dev warns that it doesn't run daemons, and vercel build doesn't build them yet.deb48cd: Accept a flat schedules format in vercel.json that is aligned with crons (schedule plus one of path, function, topic, or entrypoint), and emi
schedules format in vercel.json that is aligned with crons (schedule plus one of path, function, topic, or entrypoint), and emit schedules in the flat format in Build Output API config.json. The nested expression/target format is still accepted.ff3d2f7: Allow projects to temporarily extend Node.js 20 support through November 1, 2026.
5082546: Build Python schedule entrypoints. A .py entrypoint such as jobs/nightly.py runs as a script once per firing in a private function under _ver
5082546: Build Python schedule entrypoints. A .py entrypoint such as jobs/nightly.py runs as a script once per firing in a private function under _vercel/schedules/. Entrypoints with the same functions config share one function, which runs the script for the dispatched schedule name, so the project's dependencies are bundled once per distinct config instead of once per script. Entrypoints without functions config share _vercel/schedules/default; the others' function is named after the functions patterns their config came from, such as _vercel/schedules/jobs/report. Schedule names must be unique within a shared function.
Declared schedule entrypoints are not served as static files, but other files follow the normal static rules. When a project with Python schedule entrypoints publishes other .py files from its root, through the zero-config static fallback or outputDirectory: ".", vercel build now warns and lists them.
Add findMatchingFunction to @vercel/build-utils, which returns the functions entry that applies to a function.
34b2c8e: Support afterCacheBypass rules in Build Output API config.json, preserving request and cached response header conditions through builds and d
afterCacheBypass rules in Build Output API config.json, preserving request and cached response header conditions through builds and deserialization.6e68e60: Add onMiss to Prerender.
6e68e60: Add onMiss to Prerender.
onMiss?: 'sync' | 'dynamic';
Declares how a request is served when no prerendered output is available for
it yet. Absent means sync: block the response on rendering it. dynamic
serves the request dynamically while the static shell is regenerated in the
background. The value is carried unvalidated so an unknown mode cannot fail
a deploy.
888f59e: Define an optional builder-owned development manifest for function identities, local invocation targets, trigger metadata, and native schedul
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.53a6086: Remove payload from static schedule configuration in vercel.json. Static schedules no longer accept or expose a payload field; use dynamic sc
payload from static schedule configuration in vercel.json. Static schedules no longer accept or expose a payload field; use dynamic schedules for payload support.f9d0e90: Add experimental Cloud Native Buildpacks lifecycle support with isolated source staging, pinned lifecycle and buildpack archives, and runtime
.ruby-version, .tool-versions, or
the tools.ruby entry in mise.toml, then an exact Gemfile declaration,
defaulting to Ruby 3.4. Unsupported version declarations fail with configuration
guidance. Nothing selects a buildpack yet.bun install silently discarding bun.lock files with lockfileVersion: 2 (written by Bun >= 1.4). The install step now selects the Bun 1.4 binary whenever the lockfile requires it, mirroring how the pnpm version is already inferred from its lockfile version, instead of always running the container's default Bun 1.3.x install.54a6d73: 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 de
timezone to schedules in vercel.json and Build Output API config. Omitted timezones use UTC. Validate configured timezones before building.55e8d1e: Reduce CLI startup and deployment preparation time through lazy shared dependencies, smaller bundles, parallel Git metadata and file collecti
55e8d1e: 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.
b174f14: Raise the client-side maxDuration validation limit to 3600 seconds.
maxDuration validation limit to 3600 seconds.1817491: Delay the pnpm 11 created-at default so unpinned lockfile 9.0 projects stay on pnpm 10. pnpm 11's default minimumReleaseAge of 1 day was brea
minimumReleaseAge of 1 day was breaking installs of freshly published packages. Explicit packageManager / devEngines pins to pnpm 11 are unchanged.392c759: Honor pnpm 12 pins without auto-adopting, and stop passing --unsafe-perm to pnpm install.
392c759: Honor pnpm 12 pins without auto-adopting, and stop passing --unsafe-perm to pnpm install.
When Corepack is off, a lockfile-compatible packageManager / devEngines.packageManager / engines.pnpm pin for 12.x selects /pnpm12 if that directory exists. Unpinned lockfile 9.0 still defaults to pnpm 9/10/11 by project creation date. pnpm install no longer includes --unsafe-perm, which pnpm 12's Rust CLI rejects.
a652a99: Propagate top-level schedules from vercel.json into the Build Output API config.json during vercel build, and validate the property against t
schedules from vercel.json into the Build Output API config.json during vercel build, and validate the property against the schedules schema37ff9da: Add build type to deploy manifest.
schedule/v1beta triggers in the Lambda runtime validation and the functions config schemaaad9541: Run on-disk JavaScript workers with a lazily resolved system Node.js executable in native CLI installations, and install the matching Build U
a443e57: Revert dependency install log rewriting that piped pnpm stdout through an unread Transform and could hang large installs.
90afd71: Expose the resolved rewrite destination as the request path observed by Node backend framework applications (express, hono, h3, koa, nestjs,
f8add0a: Replace prerenderClassification on Prerender with initialMetadata.
f8add0a: Replace prerenderClassification on Prerender with initialMetadata.
The platform consumes only the request-time compute mode and the HTML shell
size, so the flattened four-field taxonomy (routeType, response,
compute, htmlSize) is reduced to a single grouped field:
initialMetadata?: {
compute: 'blocking' | 'resuming' | 'static';
htmlSize?: number;
}
The group is named initialMetadata because the values describe the
deployment as it was built: revalidation can regenerate a route's output over
the deployment's lifetime, so readers must treat them as initial values, not
live state. @vercel/next reads compute and htmlSize off the v4
prerender-manifest taxonomy and deliberately ignores routeType and
response; the values are still carried unvalidated so a compute mode added
by a future framework release cannot hard-fail a deploy, and they are still
set only on the primary output of each prerender group. htmlSize: 0 is a
real size (a shell that postponed everything); htmlSize is absent when
there is no HTML shell to measure (route handlers, Pages Router). Absence of
the whole group remains legitimate (notFoundRoutes, Pages Router
fallback: false, older frameworks).
cd6b038: Honor package.json pnpm pins without Corepack, and default new projects to pnpm 11.
cd6b038: Honor package.json pnpm pins without Corepack, and default new projects to pnpm 11.
When Corepack is off, devEngines.packageManager is preferred, then a lockfile-compatible packageManager field, then engines.pnpm as a selector. Unpinned lockfile 9.0 projects created on or after 2026-08-19 use pnpm 11 (Node 22+) if /pnpm11 is present in the build image; otherwise they keep pnpm 10.
e340c58: Add schedules/v1beta to TriggerEvent types
b4f09c1: Support selecting Bun 1.4.x as an explicit runtime and build-time package manager, including local Bun servers.
852e1a0: Move middleware matcher utils from node builder to general build utils.
2da7809: Remove redundant and ineffective package tests.
13f81ac: Support pnpm lockfiles containing multiple YAML documents.
d72826e: Prevented unit tests and generated outputs from changing Turborepo task inputs during CI, and removed the redundant affected Unit test retry.
b7ec19b: Scope the pre-compilation install's VERCEL_INSTALL_COMPLETED marker to the package.json it installed. Previously, a vercel.toml/vercel.ts con
VERCEL_INSTALL_COMPLETED marker to the package.json it installed. Previously, a vercel.toml/vercel.ts config caused vc build to install at the repo root and then silently skip every later default install, so services whose install root is a different workspace (its own package.json/lockfile) built without dependencies.6d7fbfa: Bump all workspace packages to trigger a full publish from vercel-internal.
a69c714: Propagate per-function maxConcurrency configuration into build outputs and keep every configured Next.js route in its own Lambda group, inclu
maxConcurrency configuration into build outputs and keep every configured Next.js route in its own Lambda group, including routes with the same limit.2c75803: Preserve 4-byte UTF-8 characters when streaming string FileBlob contents (fixes Edge Function corruption during vercel build).
FileBlob contents (fixes Edge Function corruption during vercel build).17ee736: Replace the vercel-workers integration for Python queue subscribers and workflows with the new vercel-queue SDK:
17ee736: Replace the vercel-workers integration for Python queue subscribers and workflows with the new vercel-queue SDK:
[[tool.vercel.subscribers]] entrypoints are introspected at build time via vercel.queue.get_subscriptions() and served through generated vercel.queue.asgi_app() handler modules, with queue/v2beta triggers carrying the SDK-registered consumer groups and per-subscription tuning.vercel-celery/vercel-dramatiq integration package injected automatically (bundled variant unless vercel-queue is an explicit dependency), in builds and in vercel dev.[[tool.vercel.workflows]] entrypoints follow the SDK generation: projects on vercel >= 0.8.0 are served through vercel-queue like subscribers; older or undeterminable versions keep the legacy vercel-workers serving (worker env markers, injected pinned vercel-workers).vercel-workers directly keep the legacy integration wholesale: legacy subscriber schema, direct entrypoint serving, worker env markers.vercel dev serves queue sidecars through vercel.queue.asgi_app() for new-SDK projects, and its queue broker delivers with the SDK-registered consumer groups introspected at sidecar startup (matching production trigger behavior); legacy projects keep the vercel-workers bootstrap.config.hasWorkerServices; the Python builder makes all queue-serving decisions from project metadata.4502520: Support Node.js Routing Middleware entrypoints through proxy.entrypoint, with optional path matching through proxy.matcher. The matcher may b
proxy.entrypoint, with optional path matching through proxy.matcher. The matcher may be configured in the entrypoint source or vercel.json, but not both.7dd4301: Make service bindings type optional.
One column per quarter.