Node.js 20 Hit End of Life in April. Are Your Data Jobs Still on It?

Node.js 20 is past its last release

Node.js 20 came out in April 2023 under the codename Iron. For a couple of years it was the safe default, so a lot of small data jobs were built on it. Think of the AWS Lambda hook that picks up a vendor file and drops it into a bucket. Or the Azure Function that moves a report from one share to another. Or the Google Cloud function that kicks off a nightly load. Or the Docker image that still pins Node 20 because nobody touched it after the last release.

The Node release schedule lists the end of life for version 20 as April 30, 2026. At that point the release stops getting fixes from the people who make Node. The code keeps running exactly as before. That is why it is easy to miss.

The cloud platforms have their own dates

AWS lists nodejs20.x on its Lambda deprecated runtimes table with a deprecation date of April 30, 2026. Creating new functions on it gets blocked on July 29, 2027. Updating existing functions gets blocked on August 31, 2027. The runtime sat on Amazon Linux 2023. AWS says that after a runtime is deprecated it may no longer apply security patches or updates, and functions using it are no longer eligible for technical support.

Azure Functions now lists only Node.js 24, supported until April 30, 2028, and Node.js 22, supported until April 30, 2027. Node.js 20 is gone from the supported languages page. If a function app is still pinned to 20, the upgrade is overdue.

Google lists nodejs20 for Cloud Run functions with a deprecation date of April 30, 2026 and a decommission date of October 30, 2026. After decommission, Google says you can no longer create new workloads or update existing ones on that runtime, and workloads that keep using it may be disabled. That October date is closer than the AWS block dates, so Google Cloud functions deserve first attention.

Where Node 20 hides in an Oklahoma company

It is rarely one big system. It is a dozen small jobs that belong to different people. These are the places to look.

1. 1AWS Lambda functions still set to the nodejs20.x runtime.
2. 2Azure Functions apps still pinned to Node 20.
3. 3Google Cloud functions still set to nodejs20.
4. 4Docker images built on the official Node 20 image.
5. 5Build pipelines in GitHub or Azure DevOps that pin Node 20.
6. 6Local scripts and tools on one engineer's laptop that feed a weekly report.

None of those jobs has to be large. A fifty line function that moves a CSV every morning is enough to break a load when the runtime cannot be updated. The person who wrote it may have left. The cloud account email may go to a shared inbox. So the first sign of trouble is often a failed deploy on the day you need a quick fix.

Why this one slips through

Nobody gets an error message the day after end of life. The job that loads inventory still finishes at 2 in the morning. Security reviews may flag the runtime months later, or not at all. Cloud notices go out before deprecation, and those emails often land in an inbox nobody reads. By the time someone notices, the block dates are already on the calendar.

Quick ways to find it

Start in the cloud consoles. The function list in AWS Lambda shows the runtime for each function, so you can sort by it and see the nodejs20.x ones in a few minutes. Check every region and every account, because old test accounts tend to hold the forgotten ones. In Azure, open each Function App and check the Node version. In Google Cloud, list functions by runtime and look for nodejs20.

On servers and in code, search your repositories for Node 20 in Dockerfiles, package files and build files. Look for an engines field that pins 20, and for base images that still say node 20. Then talk to the people who own the nightly jobs. The scripts on their laptops often feed reports that leadership reads every week, and nobody in IT knows they exist.

Keep the list simple. A shared spreadsheet with the job name, owner, where it runs, Node version and the date it last ran is enough. That list becomes the plan, and it also tells you which jobs nobody uses anymore. Those can be turned off instead of upgraded.

Which version to move to

Node.js 22 reaches end of life on April 30, 2027 under the codename Jod. Node.js 24 reaches end of life on April 30, 2028 under the codename Krypton. Node.js 26 is listed through April 30, 2029 under the codename Lithium. Moving only to 22 buys less than a year of runway from today. For most data jobs we would pick Node 24 so you only do the work once, unless a library you depend on is not ready for it yet. In that case Node 22 is still supported on AWS, Azure and Google, and you can plan the next step early.

On Lambda, nodejs22.x and nodejs24.x both run on Amazon Linux 2023, same as nodejs20.x did. That helps with compiled addons, but you still need to rebuild and test anything that ships native code. Most simple scripts move with few changes. The time goes into testing and into the one or two jobs that pinned an old package years ago.

A plan for the next 90 days

1. 1Make a list of every Node job, function and container. Note the owner, where it runs and the Node version.
2. 2Start with Google Cloud functions, since decommission is set for October 30, 2026.
3. 3Move Azure Functions off Node 20 next, because the supported list already dropped it.
4. 4Then move AWS Lambda functions before the July 2027 create block and the August 2027 update block.
5. 5Build a copy of each job on Node 22 or Node 24 and run it against a day of real input in a test area.
6. 6Compare the output with the old job before you switch.
7. 7Rebuild any package with compiled code for the new runtime.
8. 8Switch one job at a time and keep the old one ready to roll back for a week.
9. 9Put the next end of life date for each job on a shared calendar so this does not surprise you again.

What this means if you run a company in Oklahoma

Plenty of Oklahoma businesses run on small Node jobs that nobody thinks about until they break. A manufacturer in Tulsa, an energy firm in Oklahoma City or a clinic group in Norman can each have a handful of these jobs keeping reports and loads alive. Node.js 20 reaching end of life is a good reason to find them all, give each one an owner and move them before the cloud dates arrive.

At Oklahoma Data Partners, we work only with data and only in Oklahoma. We help companies list their data jobs, move them to a supported Node version and test the results before anything goes live. If you want help finding what still runs on Node 20, book a consultation.