DeprecateWatch

End-of-life dates for SDKs, cloud runtimes and open-source projects

A static, machine-readable archive of deprecation and end-of-life (EOL) dates across 489 products — languages, frameworks, databases, operating systems, server applications and managed cloud services. Every date is taken from an upstream source and dated; snapshot .

489products tracked
9,417release cycles
7,480cycles past EOL
572EOL dates in the next 365 days
176EOL dates in the next 90 days

Reaching end of life within 90 days

176 cycles pass their published EOL date between 2026-11-18 and 2027-02-16. Showing the first 40.

ProductCycleEOL dateWhenLatest release
GitLab19.32026-11-19in 1 day19.3.9
GitLab Runner19.32026-11-19in 1 day19.3.6
Bamboo10.12026-11-20in 2 days10.1.1
Jira Service Management10.22026-11-20in 2 days10.2.1
Jira Software10.22026-11-20in 2 days10.2.1
Palo Alto Networks Cortex XDR agent9.12026-11-22in 4 days9.1.0
Apache Spark4.02026-11-23in 5 days4.0.5
Stormshield Management Center3.82026-11-23in 5 days—
Anthropic Claudeclaude-opus-4-5-202511012026-11-24in 6 days—
Discourse2026.92026-11-24in 6 days2026.9.2
Firefox1602026-11-24in 6 days160.0.1
Longhorn1.92026-11-27in 9 days1.9.2
Angular202026-11-28in 10 days20.3.35
Kirby42026-11-28in 10 days4.9.7
Tarantool3.32026-11-29in 11 days3.3.5
Ansible-core2.192026-11-30in 12 days2.19.15
Anthropic Claudeclaude-sonnet-4-5-202509292026-11-30in 12 days—
Azure Kubernetes Service1.342026-11-30in 12 days—
Bellsoft Liberica JDK82026-11-30in 12 days8u513+9
IBM AIX7.3.22026-11-30in 12 days7.3.2
LibreOffice26.22026-11-30in 12 days26.2.7
Looker26.122026-11-30in 12 days—
Red Hat Satellite6.172026-11-30in 12 days6.17.13
Red Hat build of OpenJDK82026-11-30in 12 days1.8.0.472.b08-1
Fedora Linux432026-12-01in 13 days43
OpenAI API Modelsgpt-image-1.52026-12-01in 13 days—
OpenAI API Modelsgpt-image-1-mini2026-12-01in 13 days—
OpenAI API Modelschatgpt-image-latest2026-12-01in 13 days—
Redis8.02026-12-01in 13 days8.0.6
Amazon EKS1.342026-12-02in 14 days1.34-eks-33
Ceph192026-12-02in 14 days19.2.7
Bitbucket9.42026-12-03in 15 days9.4.27
Amazon Neptune1.2.1.22026-12-04in 16 days1.2.1.2
Amazon Neptune1.2.1.12026-12-04in 16 days1.2.1.1
Amazon Neptune1.2.1.02026-12-04in 16 days1.2.1.0.R7
Amazon Neptune1.2.0.22026-12-04in 16 days1.2.0.2.R6
Amazon Neptune1.2.0.12026-12-04in 16 days1.2.0.1.R3
Amazon Neptune1.2.0.02026-12-04in 16 days1.2.0.0.R4
Amazon Neptune1.1.1.02026-12-04in 16 days1.1.1.0.R7
Docker Engine25.02026-12-04in 16 days25.0.18

See the full month-by-month EOL calendar →

AWS Lambda runtime deprecations

Deprecation dates published in the AWS Lambda runtimes documentation. AWS blocks new functions 30 days after deprecation and updates 60 days after.

RuntimeIdentifierDeprecation dateWhenStatus
OS-only Runtimeprovided.al22026-07-31110 days agoEnd of life
Python 3.10python3.102026-10-3118 days agoEnd of life
.NET 8dotnet82026-11-108 days agoEnd of life
.NET 9 (container only)dotnet92026-11-108 days agoEnd of life

Recent deprecation announcements

Deprecation and retirement notes from vendor release feeds, newest first, as quoted from the source title and summary.

All 31 announcements →

Browse by category

Questions this page answers

What is DeprecateWatch?

DeprecateWatch is a static archive of end-of-life and deprecation dates for 489 SDKs, runtimes, frameworks, databases, operating systems and cloud services. It holds 9,417 release cycles and is rebuilt every day from upstream sources. The snapshot on this page is dated 2026-11-18.

Where do the dates come from?

Cycle and support dates come from the endoflife.date API (MIT licensed). AWS Lambda runtime deprecation dates come from the AWS Lambda documentation table. Deprecation announcements come from the Google Cloud release notes feed, the Azure service updates feed, AWS What's New and GitHub release feeds. Every row links to the source it was read from, and no date is estimated or filled in by hand.

How many tracked versions are already end-of-life?

As of 2026-11-18, 7,480 of 9,417 tracked release cycles have passed their end-of-life date, 230 are past active support but not yet at end of life, and 176 reach end of life within the next 90 days.

What does the Security-only status mean?

Security-only means the cycle is past the end of its active support window but its published end-of-life date has not arrived yet, so the upstream project no longer ships regular updates for it. End of life means the published EOL date has passed. No EOL date means the project has not published an end-of-life date for that cycle in the source data.

Does DeprecateWatch recommend which version to upgrade to?

No. Each product page shows two facts only: the newest cycle that is still supported for that product, and any replacement the upstream source itself states (for example a recommended model or successor). We do not rank vendors, score alternatives or issue migration advice.

How fresh is the data and how is it updated?

The snapshot shown here was generated on 2026-11-18T10:24:53+09:00 (Asia/Seoul). A scheduled job re-fetches every source daily and rebuilds these pages, so the as_of date in every table header matches the snapshot you are reading. Machine-readable copies are at /api/eol.json, /api/products.json, /api/upcoming.json and /api/announcements.json.

Using this data

The same snapshot is published as JSON, so an assistant or a script can answer "is X end of life, and when" with a dated value instead of a training-cutoff guess: