Runtime housekeeping, nothing more. Vercel regularly clears old Node.js versions off its platform - every host that takes its runtime lifecycle seriously does this. Node.js 20 is next.
Fact
The facts: on 14 July 2026 Vercel announced in its changelog that Node.js 20 is being deprecated. From 1 October 2026 the version is removed as an option in Project Settings - but only for NEW deployments. Existing deployments, already running on Node 20, keep working unchanged. The recommended upgrade is Node.js 24 - set via the engines.node field in package.json ("24.x"). Source: vercel.com/changelog/node-js-20-is-being-deprecated.
Here's what people skimming the headline miss - 'deprecated' doesn't mean 'your site dies on 1 October'. Your live deploy on Node 20 stays alive. The trap is elsewhere. The first time you push a new build after that date without bumping the version, it fails. Simply because package.json has sat untouched for months and nobody thought about the version.
The old thing doesn't die suddenly. It just stops waiting for you.
The change is one line in package.json - five minutes of work today. Leave it for October and you'll find it exactly when you don't have the time, mid-deploy on something else, under pressure.
Official primary sources
Vercel - Node.js 20 is being deprecated, 14.07.2026The visual is generated code-art, no third-party images.