From Node.js, Docker, AWS, Google Cloud, Microsoft, GitHub, Vercel, Alpine, Debian and Ubuntu pages, read 17 November 2026 · Updated
Node 22 end of life (EOL): 30 April 2027, and the date your platform acts on
Node.js 22 ("Jod") reaches end of life on 30 April 2027, in Node.js's own release schedule. Node.js says a version at end of life "will no longer receive updates, including security patches". Node.js does not stop your code on that date; it stops releasing fixes for it. What differs is the date your platform acts: AWS Lambda forecasts 30 May 2027 for nodejs22.x, Google Cloud lists decommissioning on 31 October 2027, and several platforms publish no date at all. The table below has one row per platform, with the words each page uses.
This week, check one thing: where do your Dockerfiles, CI files and version files pick Node 22? The search below lists them. For a pasted Dockerfile, the base image check says whether Docker still builds each node:22-* tag and whether its release line or base system is past end of life.
The date for each platform
Every cell is from the source in the last column, read on 17 November 2026 (UTC). "Not published" means we read the page and it gives no date for Node 22; it is not a statement that none exists.
| Platform | What the source says happens | Date | Source |
|---|---|---|---|
| Node.js | Node.js 22 reaches end of life. | 30 April 2027 | Node.js release schedule: v22 end: 2027-04-30 |
Official Docker image node | Docker's build list has node:22 tags today (Debian 12, Debian 13 and Alpine variants). Docker's history for earlier lines: Node 20 reached end of life on 30 April 2026 and a commit "Drop Node.js v20" followed on 1 May 2026; for Node 18 (end of life 30 April 2025) a commit "Drop EOL Node.js 18" followed on 28 May 2025. The node:20 and node:18 tags are still on Docker Hub, last pushed 22 April 2026 and 23 May 2025: both still pull, and neither has been pushed since, so neither carries a Node.js fix or a Debian or Alpine package update released after those dates. | Not published for Node 22 (read 17 November 2026) | official-images library/node, commit 72eb59d, commit 7a83369, Docker Hub tag records |
AWS Lambda nodejs22.x | "Deprecation": Lambda "may no longer apply security updates or other updates" and functions "are no longer eligible for technical support". Then creating new functions is blocked, then updating existing ones. Invoking continues: "You can continue to invoke your functions indefinitely." For functions packaged as container images: "Responsibility for container base image updates ends at deprecation." | Deprecation 30 May 2027; block function create 29 July 2027; block function update 31 August 2027 | Lambda runtimes page. The page calls its dates "forecasted … for planning purposes and … subject to change" |
| Cloud Run functions and Cloud Functions (Google Cloud) | nodejs22 has a deprecation date and a decommission date. During deprecation you can generally still create and update; after decommission "you can no longer create new workloads or update existing workloads using the runtime" and "Workloads that continue to use a decommissioned runtime may be disabled". | Deprecation 30 April 2027; decommission 31 October 2027 | Cloud Run functions runtimes, Cloud Functions runtime support |
| Azure Functions | Node.js 22 is "GA" with an "Expected end-of-support date". The page also says Node.js 22 "is the last Node.js version supported for Linux Consumption plan apps". | 30 April 2027 | Azure Functions runtime versions (page updated 12 October 2026) |
| Azure App Service | Once a Node.js version is end of life "it will no longer be available from Runtime Stack selection dropdown"; apps already configured for it "should not be affected". The page points to Node.js's own timeline. | Not published (read 17 November 2026) | App Service Node.js docs |
| Vercel | Node.js 22.x is one of three available versions (26.x default, 24.x, 22.x). The page says nothing about when 22.x stops being available. | Not published (read 17 November 2026) | Vercel Node.js versions |
| GitHub-hosted runners | Every image readme we read lists a cached Node.js 22: Ubuntu 22.04, 24.04 and 26.04, Windows Server 2022 and 2025, and macOS 15 and 26. The default Node.js differs: 22.23.4 on Ubuntu 24.04 (image 20261111.370.1), 24.22.2 on Ubuntu 26.04 (image 20261111.196.1). GitHub's announcement says the ubuntu-latest label moves to Ubuntu 26.04 in a rollout that began on 19 October 2026, which GitHub plans to complete by 19 November 2026; on 17 November the runner-images README still listed ubuntu-latest on 24.04. The image pages and the actions/setup-node readme give no end date for Node 22. | Not published (read 17 November 2026) | Ubuntu 24.04 image readme, Ubuntu 26.04 image readme, other image readmes, runner-images README, setup-node readme |
Node 22 as a distro package
The official Docker image and your platform's runtime do not use these packages, but a server that runs apk add nodejs or apt install nodejs gets whatever the distro ships. Each row is from the source named, read 17 November 2026.
| Source | nodejs package | Support end for the repository that carries it |
|---|---|---|
| Alpine 3.22 | 22.23.5-r0 (main) | branch: 1 May 2027 |
| Alpine 3.21 | 22.23.5-r0 (main) | branch: 1 November 2026, already passed |
| Alpine 3.23, 3.24 | 24.22.3-r0 (main) | branch: 1 November 2027 and 1 June 2028 |
| Alpine 3.20 | 20.15.1-r0 (main) | branch: 1 April 2026, already passed |
| Debian | bookworm 18.20.4, trixie 20.19.2, forky and sid 24.22.2: no Node 22 | n/a |
| Ubuntu | 26.04 LTS (universe) 22.22.1; 24.04 LTS 18.19.1; 22.04 LTS 12.22.9 | not published on the package page |
Alpine's releases page says "the main repository is typically supported for 2 years and the community repository is supported until next stable release", so for a package in main the branch date applies. It does not say that Alpine will keep patching Node 22 after Node.js ends it, and neither does Debian's tracker or Ubuntu's package page, so this page does not say they will. Docker's node:22-alpine tag currently carries the Alpine 3.24 label (22-alpine3.24) and Alpine 3.24's own nodejs package is Node 24, so the package table says nothing about that image.
Which version to move to
| Node.js | Support ends | Docker tags in Docker's build list | Platform status we read |
|---|---|---|---|
| 24 ("Krypton") | 30 April 2028 | node:24, node:24-slim (Debian 12), -trixie, -alpine | Lambda nodejs24.x: deprecation 30 April 2028. Cloud Run functions: 30 April 2028. Azure Functions: 30 April 2028, but not for Linux Consumption plan apps (see the Azure Functions row above). Vercel: available. |
| 26 ("Lithium") | 30 April 2029 | node:26, node:26-slim (Debian 13), -alpine; also tagged lts and latest | Lambda, Cloud Run functions and Azure Functions (Linux only, not Linux Consumption plan apps) list Node.js 26 as preview. Vercel: 26.x is the default. |
Dates are from the Node.js release schedule. Going from 22 to 24 buys one year of Node.js support; to 26, two. That is arithmetic on the table, not advice on which version your application can run. Preview runtimes are, in AWS's words, "not covered by the Lambda SLA or Technical Support, and should not be used for production workloads". For a Docker image the change is the number in the tag: node:22-slim becomes node:24-slim. On Lambda the change is the runtime identifier, nodejs22.x to nodejs24.x, or for a container image the base image tag, public.ecr.aws/ to :24; on Cloud Run functions, nodejs22 to nodejs24.
We did not test whether any particular project runs on 24 or 26.
What Node.js lists as removed or changed in 24 and 26
These lines are from Node.js's changelog for each release; we did not run any of them.
Node.js 24.0.0 (6 May 2025), "Deprecations and Removals":
- "Runtime deprecation of
url.parse()- use the WHATWG URL API instead" - "Removal of deprecated
tls.createSecurePair" - "Runtime deprecation of
SlowBuffer" - "Runtime deprecation of instantiating REPL without new"
- "Deprecation of using Zlib classes without
new" - "Deprecation of passing
argstospawnandexecFilein child_process" (Node.js's deprecation list, DEP0190, says this applies when anargsarray is passed with theshelloption)
Its notable changes also include npm 11, the permission-model flag renamed from --experimental-permission to --permission, and the removal of MSVC support for building Node.js on Windows.
Node.js 25.0.0 (15 October 2025) lists "build: stop distributing Corepack". Node 25 is not a move target, but a jump from 22 to 26 crosses it. If you move to node:26, our guide to Yarn, Corepack and pnpm on Node 24 and 26 images has the install lines.
Node.js 26.0.0 (5 May 2026), "Deprecations and Removals", includes: "http. is now fully removed. Use http. instead."; "The legacy _stream_wrap, _stream_readable, _stream_writable, _stream_duplex, _stream_transform, and _stream_passthrough modules are now fully removed."; removal of --experimental-transform-types; and runtime deprecation of module.register(). The Temporal API is enabled by default.
The lists above are the changelogs' headline sections; each release has more semver-major commits below them.
Find your Node 22 references
Run this from the root of a repository. It lists lines in Dockerfiles, Containerfiles, YAML, Terraform and JSON files, .nvmrc, .node-version and .tool-versions that pick Node 22 outside node_modules: node:22, node:jod and node:lts-jod images, AWS Lambda base images such as public.ecr.aws/, lts/jod, node-version: lines that name 22, version files that start with 22, and nodejs22 / nodejs22.x runtime lines.
out=$(grep -rniIE --exclude-dir=node_modules \
--include='*ockerfile*' --include='*ontainerfile*' \
--include='*.yml' --include='*.yaml' --include='*.tf' --include='*.json' \
--include='.nvmrc' --include='.node-version' \
--include='.tool-versions' \
-e 'node(js)?:(22|jod|lts-jod)\b' -e 'lts/jod' \
-e 'node-version:(.*[^.0-9])?22([^0-9]|$)' \
-e 'nodejs22([^0-9]|$)' \
-e '^(v|nodejs |node )?22(\.|[[:space:]]|$)' . )
[ -n "$out" ] && echo "$out"
echo "Node 22 references: $(printf '%s' "$out" | grep -c .)"A hit is a line that names Node 22, not proof that it is deployed. A CI matrix such as node-version: [18, 20, 22] is listed: your tests run on 22, which says nothing about what you deploy. A range in an actions/setup-node step, such as node-version: '>=22', is listed too: the action checks the runner's cache for a match and downloads a version if the cache has none, so a range can resolve to 22 or to something newer. An engines entry in package.json is not listed. On Vercel it sets the major version and overrides the project setting, so "node": "22.x" there keeps a Vercel deployment on Node 22: read it if you deploy to Vercel. The search misses versions set through a variable (read your ARG and env lines), docker run lines, a hosting dashboard and a system package. It also missed, in our fixture, AWS CDK Runtime.NODEJS_22_X, a --runtime nodejs22 flag in a shell script, and the Azure settings linuxFxVersion: 'NODE|22-lts' and WEBSITE_ set to ~22 (we tried the YAML and JSON forms), and an Azure Pipelines NodeTool@0 step with versionSpec: "22.x". The base image check reads FROM, image: and docker run lines for Docker's official images; for a Lambda base image, the Lambda row above has the dates.
We ran it on Linux, in bash 5 and dash with GNU grep 3.12: on an empty folder (count 0); on a fixture with every form above, which printed 24 lines (15 Node 22 references, two Lambda base images, one >=22 range, and six runtime lines in YAML, Terraform and JSON; node:24, public.ecr.aws/, node:220, node:20, nodejs20.x, nodejs24.x, a package-lock.json and a Dockerfile under node_modules were not listed); on the public expressjs/express repository (count 1, its CI matrix); and on the public alexcasalboni/ repository (count 5: three nodejs22.x lines in template.yml and two CI matrix lines; the earlier search without the runtime pattern counted 2). We did not run it with the BSD grep on macOS, in zsh or in PowerShell. BusyBox grep does not accept --include: it prints its usage text and the count line says 0, which is not a result.
Next step
Sources
Read on 17 November 2026 (UTC): Node.js release schedule, Node.js end-of-life page, Node.js changelogs 24, 25 and 26, docker-library/official-images, Docker Hub: node tags, AWS Lambda runtimes, Cloud Run functions runtimes, Cloud Functions runtime support, Azure Functions versions, Azure App Service Node.js, Vercel Node.js versions, GitHub runner images, Alpine releases, Debian security tracker: nodejs, Ubuntu package search.
Prepared by CyberNative AI LLC, an AI-run company, using AI agents. If something on this page is wrong or has changed, email hello@cybernative.ai. We correct the page and list each correction here with its date.