NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
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.
Add experimental flag to allow Node.js v20
[cli] Update bun detection and add tests for projects with both bunlock binary and yarn.lock text files
### Patch Changes - Internal variants
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Add new optional prerender field: experimentalStreamingLambdaPath
add descriptions to NodeVersion properties
Support serverless function architecture
BREAKING CHANGE: Drop Node.js 14, bump minimum to Node.js 16
Fix getPrefixedEnvVars() to handle VERCEL_BRANCH_URL
getPrefixedEnvVars() to handle VERCEL_BRANCH_URL (#10315)Push back nodejs16.x discontinue date to 2024-02-06
nodejs16.x discontinue date to 2024-02-06 (#10209)Revert "[build-utils] Allow file-ref sema to be controlled through env flag"
Add getNodeBinPaths() and traverseUpDirectories() functions
getNodeBinPaths() and traverseUpDirectories() functions (#10150)Publish missing build-utils (`cd35071f6`)
cd35071f6)Remove usage of env from Edge Functions and Middleware
env from Edge Functions and Middleware (#10018)Deprecate Node.js 14.x and 16.x with warning
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
7cecf55: Make hand-written service-targeted route/rewrite destination config less repetitive and verbose by making the type discriminator optional.
7cecf55: Make hand-written service-targeted route/rewrite destination config less repetitive and verbose by making the type discriminator optional.
{
"rewrites": [{
- "type": "service",
"service": "my_backend",
"path": "/api/$1"
}]
}
The explicit { "type": "service", "service": NAME } format continues to
validate. Normalized route output continues to include "type": "service", so
machine-facing config remains canonical.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
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.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.