ST-2026-020 · Runtimes & developer platforms
Vercel disables Node.js 20 for new Builds and Functions deployments on 1 October
Vercel will disable Node.js 20 in project settings on 1 October 2026, causing new deployments that still target Node.js 20 to fail while already-deployed Serverless Functions continue to invoke.
Previous state
Projects could select Node.js 20 for Vercel Builds and Functions and create new deployments using that managed runtime.
Current state
Node.js 20 is removed from project settings for managed Builds and Functions; new deployments targeting it error, while existing Serverless Function deployments continue running.
Affected users
Who needs to care
Vercel projects whose managed Build or Function runtime remains pinned to Node.js 20 through project settings, package.json engines, version files or CI configuration.
Required response
What to do
Inventory affected projects, upgrade runtime pins to Node.js 24, reinstall dependencies, run build and test suites, deploy and verify process.version. Use a container only as a bounded temporary alternative and assume responsibility for its Node.js security updates.
Evidence boundary
What the source does not prove
The notice blocks new managed-runtime deployments, not invocations of existing Serverless Function deployments. Container-image deployments are outside the project-setting block, but Vercel explicitly transfers runtime and security-update responsibility to the customer.
Connected NeoLinks intelligence
Related evidence across the network
Curated because the records share a publisher, platform, control, sector or procurement context. Each destination keeps its own evidence boundary.
Vercel Functions per-unit invocation billing
Node.js 20 retirement changes deployment compatibility; SkuTrace tracks the separate Functions invocation billing model.
Vercel Hobby deployment-retention enforcement
Runtime support and deployment retention create different operational risks and are preserved as separate records.
Lifecycle history
Dated event sequence
- Upstream Node.js 20 end of life
Vercel identifies the upstream Node.js 20 end-of-life date as the trigger for its managed-runtime retirement.
- Vercel notice published
Vercel announced the affected deployment boundary, upgrade path and container workaround.
- New-deployment enforcement
Node.js 20 is disabled in project settings and new managed Builds or Functions deployments targeting it fail.
Evidence ledger
First-party sources
- 01Vercel Changelog — Node.js 20 is being deprecated on October 1, 2026
Official runtime deprecation notice · 2026-07-14
Open official source ↗