Provenance Report

We check the dates. Here's the proof.

EOL dates drift: vendors revise them after release, projections harden into “facts,” and errors propagate across every site that republishes them — ours included. So we cross-check our highest-impact products against each vendor's official lifecycle documentation, publish corrections the moment a vendor's page says otherwise, and label honestly when a vendor publishes no dates at all. This page is regenerated from our verification records at every build.

127
Products vendor-verified
372
Published corrections
6
Honestly unconfirmed
2
Under review

Machine-readable version: /verification.json

Scoreboard

The numbers this dataset competes on, recomputed from the build inputs at every build. None of them is typed by hand: the vendor-sourced shares come from the provenance class of every served date, the identifier counts from the published CPE and package-URL maps, the citation share from Microsoft's own Bing AI export of Copilot citations per page.

669
Products tracked
35.3%
All dates vendor-sourced
39.7%
Vendor-sourced on the 94 most-cited product pages
169
Products joined to CISA KEV
530 / 669
Products with a CPE
376 / 669
Products with a package URL
72
Edge platforms on the EOS list
141
Vendor pages pinned by sentinel
1
Days since the last vendor drift was caught

Identifier dispositions: 139 products are recorded as having no CPE in the NIST dictionary (each with the reason) and 0 are still undisposed; 293 are recorded as having no package URL and 0 are still undisposed. Citation source: Microsoft Bing Webmaster AI page statistics exported 2026-09-22 (415 pages; 94 of them are product pages, carrying 3194 citations). Last vendor drift caught: 2026-10-15.

Where every date comes from

Every lifecycle date we serve carries a label at build time: vendor-override (set from the vendor's own publication, source recorded), vendor-fetched (our adapter read the vendor's lifecycle page and it agrees), vendor-verified (a human cross-check covers that version), custom (our own catalog, curated from the vendor), or upstream (endoflife.date only). The commercial tier — the 319 products with a paid-support market — is the number we hold ourselves to. Feeds are re-read twice a day; a disagreement is published here until it is resolved at the vendor.

59.5%
Commercial-tier dates vendor-sourced
7321 / 12310
Commercial-tier dates
35.3%
Commercial-tier dates with two sources agreeing
82
Live vendor feeds
1
Vendor disagreements open

Confidence: a date is high confidence when two or more independent source classes agree with it — the vendor's own feed, a human decision (a published correction or verification record), the upstream dataset; medium when one source carries it; low when the vendor feed disagrees or has not been read for two weeks. The API returns the grade and the agreement count on every score (eol_date_confidence, eol_date_agreement).

ProductVendor source readLast readVersionsDates vendor-sourced
AlmaLinux AlmaLinux OS Foundation (release notes index) ↗ 2026-10-12 3 9 of 9
Amazon Corretto Amazon Web Services ↗ 2026-10-09 7 (EOL to the month) 14 of 30
Amazon EKS Amazon Web Services ↗ 2026-10-09 7 21 of 57
Angular Angular team (Google) ↗ 2026-10-12 14 (EOL to the month) 36 of 42
Apache Kafka Apache Kafka (downloads page) ↗ 2026-10-12 27 27 of 77
AWS Lambda AWS (Lambda runtimes) ↗ 2026-10-14 52 101 of 153
Bamboo Atlassian ↗ 2026-10-11 5 11 of 132
Bitbucket Atlassian ↗ 2026-10-11 12 23 of 253
Bootstrap Bootstrap team, npm registry ↗ 2026-10-12 2 2 of 10
Ceph Ceph ↗ 2026-10-15 12 24 of 24
Checkmk Checkmk ↗ 2026-10-12 3 8 of 14
Google Chrome Chrome release team (Chromium dashboard) ↗ 2026-10-16 145 289 of 296
Cisco IOS XE Cisco (End-of-Life bulletins) ↗ 2026-10-12 18 37 of 58
Citrix Virtual Apps and Desktops Citrix (Cloud Software Group) ↗ 2026-10-12 8 11 of 83
Claude (Anthropic) Anthropic (model deprecations) ↗ 2026-10-16 35 27 of 75
Adobe ColdFusion Adobe ↗ 2026-10-11 9 20 of 20
Confluence Atlassian ↗ 2026-10-11 11 21 of 173
Debian Debian Project (distro-info-data) ↗ 2026-10-12 12 28 of 61
Django Django Software Foundation ↗ 2026-10-12 20 (EOL to the month) 28 of 69
.NET Microsoft (.NET) ↗ 2026-10-12 13 26 of 26
.NET Framework Microsoft ↗ 2026-10-12 9 7 of 21
Drupal Drupal Association (drupal.org) ↗ 2026-10-12 34 24 of 60
Electron Electron ↗ 2026-10-12 43 86 of 86
Ember.js Ember.js (LTS release schedule) ↗ 2026-10-12 21 51 of 133
Envoy Envoy ↗ 2026-10-15 29 58 of 82
Firefox Mozilla (product-details) ↗ 2026-10-14 58 107 of 117
FortiOS Fortinet (product life cycle API) ↗ 2026-10-12 8 24 of 24
FreeBSD FreeBSD Project (security pages) ↗ 2026-10-14 52 104 of 178
GitLab GitLab ↗ 2026-10-16 42 122 of 204
Google Kubernetes Engine Google Cloud ↗ 2026-10-16 7 14 of 67
Horizon Omnissa (Product Lifecycle Matrix) ↗ 2026-10-12 21 42 of 48
IBM Db2 IBM (product lifecycle list) ↗ 2026-10-12 8 15 of 15
IBM i IBM (IBM i Release Life Cycle) ↗ 2026-10-12 23 53 of 56
IBM MQ IBM (product lifecycle list) ↗ 2026-10-12 7 17 of 29
IBM Netezza IBM (product lifecycle list) ↗ 2026-10-16 13 16 of 16
Istio Istio ↗ 2026-10-15 19 38 of 50
Jira Software Atlassian ↗ 2026-10-11 15 31 of 189
Kirby Kirby (security page, Supported Versions) ↗ 2026-10-12 8 16 of 42
Kubernetes Kubernetes Release Team ↗ 2026-10-12 36 47 of 64
Magento Adobe ↗ 2026-10-12 6 10 of 73
MariaDB MariaDB Foundation ↗ 2026-10-12 15 35 of 73
Mattermost Mattermost (server releases) ↗ 2026-10-12 25 50 of 114
Microsoft 365 Apps Microsoft (Update history for Microsoft 365 Apps) ↗ 2026-10-14 118 120 of 121 · 1 under review
Microsoft Edge Microsoft (Edge release schedule) ↗ 2026-10-16 68 234 of 234
Microsoft Exchange Microsoft ↗ 2026-10-12 3 12 of 31
Microsoft SQL Server Microsoft ↗ 2026-10-12 31 98 of 114
MySQL Oracle (MySQL) ↗ 2026-10-12 8 (EOL to the month) 18 of 48
Neo4j Neo4j (supported versions) ↗ 2026-09-26 (stale) 63 89 of 143
NGINX nginx (nginx.org CHANGES) ↗ 2026-10-15 32 62 of 62
Node.js Node.js Release Working Group ↗ 2026-10-12 27 69 of 72
Microsoft Office Microsoft ↗ 2026-10-12 10 28 of 30
OpenSSL OpenSSL Library project ↗ 2026-10-12 4 14 of 28
Oracle Database Oracle ↗ 2026-10-11 12 (EOL to the month) 29 of 31
Oracle JDK Oracle (Java SE Support Roadmap) ↗ 2026-10-12 7 (EOL to the month) 19 of 62
Oracle Linux Oracle ↗ 2026-10-11 8 (EOL to the month) 10 of 15
PAN-OS Palo Alto Networks ↗ 2026-10-12 24 48 of 52
PHP The PHP Group ↗ 2026-10-12 24 45 of 54
PostgreSQL PostgreSQL Global Development Group ↗ 2026-10-12 29 58 of 58
Proxmox VE Proxmox Server Solutions ↗ 2026-10-12 8 (EOL to the month) 8 of 17
Python Python Software Foundation (devguide) ↗ 2026-10-10 18 (EOL to the month) 45 of 45
Ruby on Rails Ruby on Rails core team ↗ 2026-10-12 2 4 of 33
React React team (Meta), npm registry ↗ 2026-10-12 5 5 of 9
Red Hat Ansible Automation Platform Red Hat ↗ 2026-10-14 9 20 of 20
Red Hat OpenShift Red Hat ↗ 2026-10-13 22 73 of 73
Red Hat JBoss EAP Red Hat ↗ 2026-10-12 6 24 of 24
Red Hat JBoss Web Server Red Hat ↗ 2026-10-12 6 24 of 24
Red Hat Satellite Red Hat ↗ 2026-10-11 26 58 of 58
RHEL Red Hat ↗ 2026-10-11 3 20 of 28
Rocket.Chat Rocket.Chat (Version Durability matrix) ↗ 2026-10-12 79 (EOL to the month) 158 of 237
SharePoint Microsoft ↗ 2026-10-12 3 10 of 16
Splunk Splunk (Cisco) ↗ 2026-10-16 23 32 of 32
Spring Boot Spring (Broadcom) ↗ 2026-10-12 18 (EOL to the month) 51 of 51
Spring Framework Spring (Broadcom) ↗ 2026-10-13 10 (EOL to the month) 27 of 29
Symfony Symfony SAS ↗ 2026-10-12 23 (EOL to the month) 69 of 90
Apache Tomcat Apache Tomcat project ↗ 2026-10-12 5 13 of 15
Ubuntu Canonical ↗ 2026-10-12 44 (EOL to the month) 104 of 140
Visual Studio Microsoft (Visual Studio release history) ↗ 2026-10-14 26 52 of 105
Vue.js Vue.js project (v2.vuejs.org) ↗ 2026-10-12 15 21 of 41
Windows Microsoft ↗ 2026-10-14 43 131 of 150
Windows Server Microsoft ↗ 2026-10-12 13 36 of 64
Zabbix Zabbix LLC ↗ 2026-10-12 5 7 of 25
IBM z/OS IBM (product lifecycle list) ↗ 2026-10-12 7 15 of 15

The commercial tier (published so the number above can be checked): Adobe Acrobat · Adobe Experience Manager · AlmaLinux · Amazon Corretto · Amazon EKS · Amazon Linux · Angular · AngularJS · Ansible · Apache ActiveMQ · Apache ActiveMQ Artemis · Apache Cassandra · Apache Commons · Apache CXF · Apache HTTP Server · Apache Kafka · Apache Lucene · Apache Struts · Apache Tapestry · Arista EOS · Artifactory · Atlassian Data Center · Axios · Azul Zulu · Azure DevOps Server · Bamboo · Barracuda CloudGen Firewall · Barracuda Web Application Firewall · BellSoft Liberica · BIG-IP · Bitbucket · Bootstrap · CDH (Cloudera Distribution of Hadoop) · CentOS · Check Point security gateway appliances (hardware) · Check Point Gaia · Cisco AnyConnect · Cisco ASA · Cisco ASA 5500-X Series (hardware) · Cisco Secure Firewall Management Center · Cisco Secure Firewall Threat Defense (FTD) · Cisco IOS · Cisco IOS XE · Cisco IOS XR · Cisco Identity Services Engine · Cisco Meraki · Cisco NX-OS · Cisco Small Business RV Series Routers (hardware) · Cisco Catalyst SD-WAN · Cisco Secure Email Gateway · Cisco Unified Communications Manager · XenServer (Citrix Hypervisor) · Citrix Virtual Apps and Desktops · Citrix Workspace app · Cloudera Base on Premises · Cloudera Data Flow for Cloud · Cloudera Data Services on Premises · Cloudera on Cloud · Cloudera Platform (CDP) · CloudLinux OS · CockroachDB · Adobe ColdFusion · Commvault · Confluence · Confluent Platform · Consul · Control-M · Cortex XDR · Couchbase Server · Debian · Apache Derby · Django · Dojo Toolkit · dom4j · .NET · .NET Framework · Drupal · Eclipse Jetty · Eclipse Temurin · Elasticsearch · elliptic · Ember.js · ESLint · VMware ESXi · Express · FileMaker · FortiADC · FortiAnalyzer · FortiAuthenticator · FortiClient EMS · FortiMail · FortiManager · FortiNAC · FortiNAC-F · FortiOS · FortiProxy · FortiSandbox · FortiWeb · GitLab · Grails · GraphQL Java · Google Guava · H2 Database · HAProxy · HashiCorp Vault · Hazelcast Platform · Hortonworks Data Platform (HDP) · Hibernate ORM · Horizon · HSQLDB · IBM AIX · IBM Db2 · IBM i · IBM MQ · IBM Netezza · IBM Semeru Runtime · IBM WebSphere Application Server · Ingress NGINX · Ionic · Ivanti Connect Secure · Ivanti Cloud Services Appliance · Ivanti Endpoint Manager (EPM) · Ivanti Endpoint Manager Mobile (EPMM) · Ivanti Secure Appliance (ISA / PSA) · Ivanti Policy Secure · Ivanti Sentry · Jackson · Jenkins · Jira Service Management · Jira Software · jQuery · jQuery UI · JSON-java (org.json) · JsonPath (Jayway) · Juniper EX Series (hardware) · Juniper MX and M Series (hardware) · Juniper QFX Series (hardware) · Juniper SRX Series (hardware) · Juniper Junos OS · Kaseya VSA · Keycloak · Knockout.js · Kubernetes · Lodash · Apache Log4j · Logback · LoopBack · Magento · ManageEngine Endpoint Central · MariaDB · Mattermost · Micrometer · Microsoft 365 Apps · BizTalk Server · Microsoft Build of OpenJDK · Microsoft Configuration Manager · Dynamics AX · Dynamics 365 Business Central on-premises · Dynamics CRM · Dynamics 365 Customer Engagement (on-premises) · Dynamics GP · Dynamics NAV · Dynamics SL · Microsoft Entra Connect · Microsoft Hyper-V Server · Skype for Business Server · System Center · Modernizr · Moment.js · MongoDB · Moodle · Microsoft Exchange · Microsoft SQL Server · MuleSoft Runtime · MySQL · MySQL Connector/J · Neo4j · NestJS · NetApp ONTAP · NetBackup Appliance OS · NetScaler ADC · NetScaler MPX / SDX (hardware) · Nextcloud · Next.js · Nexus · NGINX · Node.js · Nomad · NumPy · Nutanix AOS · Nutanix Files · Nutanix Prism · Nuxt · Microsoft Office · Office Online Server · OpenSSL · OpenVPN · OPNsense · Oracle ADF · Oracle APEX · Oracle Database · Oracle E-Business Suite · Oracle Forms and Reports · Oracle GraalVM · Oracle HTTP Server · Oracle Identity and Access Management · Oracle JDK · Oracle Linux · Oracle PeopleSoft · Oracle SOA Suite · Oracle Solaris · Oracle WebLogic Server · Palo Alto Networks PA-Series (hardware) · Palo Alto Expedition · Palo Alto GlobalProtect · PAN-OS · PaperCut NG/MF · Passport.js · PHP · PostCSS · PostgreSQL · PowerShell · Progress LoadMaster · Progress MOVEit Automation · Progress MOVEit Transfer · Progress WhatsUp Gold · Progress WS_FTP Server · Protocol Buffers · Protractor · Proxmox VE · Python · QNAP NAS · Quarkus · Querydsl · RabbitMQ · Ruby on Rails · React · Reactor Netty · Red Hat Ansible Automation Platform · Red Hat OpenShift · Red Hat build of OpenJDK · Red Hat JBoss EAP · Red Hat JBoss Web Server · Red Hat OpenStack Platform · Red Hat Satellite · Red Hat Virtualization · Redis · RequireJS · RHEL · Rocket.Chat · Rocky Linux · RouterOS · SAP BusinessObjects BI · SAP ECC 6.0 / Business Suite 7 · SAP NetWeaver · SapMachine · SharePoint · SLES · SnakeYAML · SolarWinds Orion Platform · SolarWinds Serv-U · SolarWinds Web Help Desk · Apache Solr · SonarQube Server · SonicWall SonicOS · SonicWall Email Security · SonicWall Email Security appliances · SonicWall Firewalls (TZ / NSa / NSsp hardware) · SonicWall Network Security Manager (NSM) On-Prem · SonicWall SMA 100 · SonicWall SMA 1000 · SonicWall SonicWave / SonicPoint access points (hardware) · Sophos Firewall · Sophos Firewall appliances · Sophos UTM · Splunk · Spring Boot · Spring Cloud · Spring Framework · Spring Security · SQLite JDBC · Symfony · Synology DSM · JetBrains TeamCity · Terraform · Thymeleaf · TinyMCE · Apache Tomcat · Trend Micro Apex Central · Trend Micro Apex One · Ubiquiti UniFi · Ubuntu · VMware vCenter · Veeam Backup & Replication · Veeam Backup for Microsoft 365 · Veeam ONE · Visual COBOL · Visual Studio · VMware Aria Automation · VMware Aria Operations · VMware Cloud Foundation · VMware NSX · VMware SRM · VMware Tools · Vue.js · Vuetify · WatchGuard Firebox · webpack · Windows · Windows Embedded · Windows Server · XCP-ng · YUI · Zabbix · Zerto · Zimbra · IBM z/OS · Zyxel NAS · Zyxel ATP/USG FLEX/USG/ZyWALL/VPN.

Source of record, in order: the vendor's published lifecycle documentation; the vendor's lifecycle API; an authoritative security or lifecycle source; a corroborated third-party dataset; endoflife.date, the upstream community dataset we also contribute to. A vendor value read twice and reproduced identically may correct upstream; a disagreement between two vendor sources is a human decision, recorded as a correction with its source.

Corrections contributed upstream

What we find does not stay here: 14 pull requests from endoflife.ai have been merged into endoflife.date (1 open).

Pull requestStatusMerged
#10928 drupal: 11.2 and 10.5 security support ended with the 11.4.0 release (2026-07-01)merged2026-09-07
#10927 splunk: 8.2 EOL extended to 2023-09-30, 8.1 release date 2020-10-19 (vendor support policy)merged2026-09-07
#10810 [debian] Update eol for 12 (bookworm)merged2026-08-25
#10759 [zabbix] Update eol date for 7.4 cyclemerged2026-08-19
#10716 netapp-ontap: correct 9.18.1 end of full support to 2029-01-31merged2026-08-11
#10715 ibm-i: add 7.4 Service Extension and 7.1 Program Support Extension datesmerged2026-08-11
#10691 [New Product] TeamCityopen—
#10681 Jenkins: add LTS 2.568, mark 2.555 as EOLclosed—
#10646 omnissa-horizon: correct 8.2503 eol, 8.2406 releaseDate and cycle 7 datesmerged2026-08-02
#10591 magento: refresh Adobe Commerce eoes dates per current lifecycle tablemerged2026-07-27
#10524 veeam-backup-and-replication: v13 end of support is November 2028merged2026-07-21
#10523 go: go1.26.0 was released 2026-02-10; adjust 1.24 eol accordinglymerged2026-07-21
#10522 ruby: 3.1 reached EOL on 2025-03-26 per ruby-lang.org branches pagemerged2026-07-21
#10521 kubernetes: update 1.31 and 1.30 eol to match k8s.io non-active branch historymerged2026-07-21
#10520 centos-stream: set Stream 10 eoas/eol to RHEL 10 full-support end (2030-05-31)merged2026-07-21
#10519 windows-server: update 2025 eoas/eol to revised Microsoft lifecycle datesmerged2026-07-21
#10512 Update EOL dates for windows-server, centos-stream, kubernetes, ruby, go and veeam-backup-and-replicationclosed—

Open disagreements — the vendor's page says one thing, the value we serve says another. Each is re-read and resolved by a published correction or an upstream pull request.

Product / version · fieldWe serveVendor publishes
Microsoft 365 Apps 2606 · eol 2026-10-13 true ↗

Published corrections

Where a vendor's official documentation says something newer or different than the community dataset we build on, we show the vendor's date and record why. We contribute these findings back to the endoflife.date project as we confirm them — a correction that lands there fixes the whole ecosystem, not just our site. We're merged contributors: on July 21, 2026 the endoflife.date maintainers accepted all six correction PRs from our latest verification audit — Windows Server, CentOS Stream, Kubernetes, Ruby, Go, and Veeam. See the full drift study. Each correction is also dated on the change record, with the value we served before, the value we serve now and the source.

Product / versionCorrected valueSourceReason
BellSoft Liberica 8 TBD (vendor has not confirmed a date) vendor source ↗ Upstream serves eol 2026-11-30 labelled Public support, but endoflife.date's own bellsoft-liberica.md says its eol column uses Eclipse Temurin EOL dates because they are the most conservative, so 2026-11-30 is the old Temurin Java 8 date, not a BellSoft date (Temurin itself now runs to 2030-12-31). BellSoft's roadmap, read 2026-10-11 three ways (curl with a browser UA, WebFetch, built-in browser), prints one Liberica JDK 8 date, the row 'JDK 8 | Mar 2014 | Jan 2019 | Dec 2030 | Mar 2031' under 'End of commercial support: Liberica JDK', with the policy sentence 'BellSoft's commercial support offers access to bug fixes, security updates, enhancements, and other necessary fixes for at least 8 years for Long Term Support (LTS) versions.' No November 2026 date appears on the page; the product page says only 'Java 8 until 2030+'. BellSoft names no end day for its free Liberica 8 builds, so eol stays false until it does (vendor floor dates rule). extendedSupport stays upstream's 2031-03-31, the month end of 'Mar 2031', pinned by sentinel bellsoft-liberica-8-commercial-support-end. Retire only when upstream carries a BellSoft-named day.
BellSoft Liberica 11 TBD (vendor has not confirmed a date) vendor source ↗ Upstream eol 2024-10-31 is Eclipse Temurin's old Java 11 date (endoflife.date's bellsoft-liberica.md: the eol column uses Temurin EOL dates), not a BellSoft date. BellSoft's roadmap, read 2026-10-11, prints one Liberica JDK 11 date, the row 'JDK 11 | Sep 2018 | Mar 2019 | Sep 2026 | Mar 2032' (End of commercial support: Liberica JDK = Mar 2032), and no end date for the free builds, which BellSoft still updates quarterly (latest 11.0.32.1, 2026-08-19). eol stays false until BellSoft names a day (vendor floor dates rule). extendedSupport stays upstream's 2032-03-31, the month end of Mar 2032. Pinned by sentinel bellsoft-liberica-8-commercial-support-end (covers rows 8, 11, 17, 21, 25).
BellSoft Liberica 17 TBD (vendor has not confirmed a date) vendor source ↗ Upstream eol 2027-10-31 is Eclipse Temurin's Java 17 date (endoflife.date's bellsoft-liberica.md: the eol column uses Temurin EOL dates), not a BellSoft date. BellSoft's roadmap, read 2026-10-11, prints one Liberica JDK 17 date, the row 'JDK 17 | Sep 2021 | Mar 2022 | Sep 2029 | Mar 2030' (End of commercial support: Liberica JDK = Mar 2030), and no end date for the free builds. eol stays false until BellSoft names a day (vendor floor dates rule). extendedSupport stays upstream's 2030-03-31, the month end of Mar 2030. Pinned by sentinel bellsoft-liberica-8-commercial-support-end.
BellSoft Liberica 21 TBD (vendor has not confirmed a date) vendor source ↗ Upstream already serves eol false ('Temurin EOL date not yet announced' in bellsoft-liberica.md); this entry pins it so a future Temurin date is not served as a BellSoft date. BellSoft's roadmap, read 2026-10-11, prints one Liberica JDK 21 date, the row 'JDK 21 | Sep 2023 | Mar 2024 | Sep 2031 | Mar 2032' (End of commercial support: Liberica JDK = Mar 2032), and no end date for the free builds. extendedSupport stays upstream's 2032-03-31, the month end of Mar 2032. Pinned by sentinel bellsoft-liberica-8-commercial-support-end.
BellSoft Liberica 25 TBD (vendor has not confirmed a date) vendor source ↗ Upstream eol 2031-09-30 is Eclipse Temurin's Java 25 date (endoflife.date's bellsoft-liberica.md: the eol column uses Temurin EOL dates), not a BellSoft date. BellSoft's roadmap, read 2026-10-11, prints one Liberica JDK 25 date, the row 'JDK 25 | Sep 2025 | TBA | Sep 2033 | Mar 2034' (End of commercial support: Liberica JDK = Mar 2034), and no end date for the free builds. eol stays false until BellSoft names a day (vendor floor dates rule). extendedSupport stays upstream's 2034-03-31, the month end of Mar 2034. Pinned by sentinel bellsoft-liberica-8-commercial-support-end.
Qt 6.12 TBD (vendor has not confirmed a date) vendor source ↗ Upstream added Qt 6.12 on 2026-10-04 with eol 2027-04-01 marked as an estimate and extendedSupport 2031-10-01. Qt names no day for the end of the open-source patch stream (it ends when the next minor is released), so eol stays false until Qt names one (vendor floor dates rule), and the Qt supported-versions table (read 2026-10-02) gives standard support until 2031-09-30. Release facts now come from upstream. Retire only when upstream carries a vendor-named day.
Qt 6.11 — vendor source ↗ Upstream now carries eol 2026-09-30 for Qt 6.11 (the day Qt 6.12.0 shipped), so the eol override was retired on 2026-10-05; the golden case qt-611-oss-end keeps guarding it. This entry now only holds the standard (commercial) support end from the Qt supported-versions table, 2027-03-17, where upstream prints 2027-03-23.
Qt 6.10 2026-03-23 vendor source ↗ Upstream's eol (OSS support) for 6.10 is an estimate (2025-10-07 plus six months, marked estimated in qt.md). Qt's rule on doc.qt.io/qt-6/qt-releases.html: patch releases for a minor continue until the next minor release is out. Qt 6.11.0 was published 2026-03-23 (datePublished on Qt's own release post), so that is the day 6.10 open-source patch releases stopped under Qt's rule. Standard (commercial) support for 6.10 runs to 2026-10-07 per Qt's table, served as extendedSupport.
Windows Server Core 2025 2034-11-14 vendor source ↗ Server Core follows the Windows Server 2025 lifecycle; same post-GA revision as windows-server/2025.
Ubuntu 18.04 — vendor source ↗ Canonical's release-cycle table (fetched 2026-08-29): 18.04 LTS Ubuntu Pro/ESM ends May 2028 (Legacy add-on May 2033). On 2026-08-29 upstream re-based every LTS extendedSupport to release-date + 10 years, putting 18.04 at 2028-04-26 — one month early, the same month-level error already corrected for 24.04. End-of-month day per site convention for month-precision vendor dates.
Ubuntu 20.04 — vendor source ↗ Canonical's release-cycle table (fetched 2026-08-29): 20.04 LTS Ubuntu Pro/ESM ends May 2030 (Legacy add-on May 2035). Upstream's 2026-08-29 release-date + 10 years re-base puts 20.04 at 2030-04-23 — one month early. End-of-month day per site convention for month-precision vendor dates.
Ubuntu 22.04 2027-05-31 vendor source ↗ Canonical lists standard support for 22.04 LTS ending May 2027; upstream 2027-04-01 is two months early (upstream moved it to 2027-06-01 on 2026-08-29, one month late — the override still holds). extendedSupport: Canonical's release-cycle table (fetched 2026-08-29) states Ubuntu Pro/ESM ends May 2032 (Legacy add-on May 2037); upstream's release-date + 10 years re-base puts it at 2032-04-21, one month early. End-of-month day per site convention for month-precision vendor dates.
Ubuntu 26.04 — vendor source ↗ Canonical's release-cycle table (fetched 2026-08-29): 26.04 LTS Ubuntu Pro/ESM ends May 2036 (Legacy add-on May 2041). Upstream's 2026-08-29 release-date + 10 years re-base puts 26.04 at 2036-04-23 — one month early. Standard support is deliberately NOT overridden: upstream's 2031-05-29 already falls inside Canonical's stated May 2031. End-of-month day per site convention for month-precision vendor dates.
Ubuntu 24.04 — vendor source ↗ Canonical's release-cycle table (fetched 2026-08-25): 24.04 LTS Ubuntu Pro/ESM ends May 2034; the optional Legacy add-on extends to May 2039. Upstream's 2036-05-31 matches neither phase and overstates ESM coverage by two years - in the dangerous direction (readers told they are covered when they are not). Upstream PR #10814 proposes the same correction; retire this override once it merges and the nightly refresh picks it up. End-of-month day per site convention for month-precision vendor dates. Note: one extendedSupport field cannot represent Canonical's three-phase lifecycle (standard 2029 / ESM 2034 / Legacy 2039); we publish the ESM date, Legacy belongs in prose.
Ubuntu 25.04 2026-01-15 vendor source ↗ vendor adapter ubuntu: the release team's list of releases publishes eol "2026-01-15", upstream "2026-01-17" (read twice, 2026-09-07); confirmed by the ubuntu-announce / Discourse end-of-life notice
Ubuntu 23.10 2024-07-11 vendor source ↗ vendor adapter ubuntu: the release team's list of releases publishes eol "2024-07-11", upstream "2024-07-12" (read twice, 2026-09-07); confirmed by the ubuntu-announce / Discourse end-of-life notice
Ubuntu 23.04 2024-01-25 vendor source ↗ vendor adapter ubuntu: the release team's list of releases publishes eol "2024-01-25", upstream "2024-01-20" (read twice, 2026-09-07); confirmed by the ubuntu-announce / Discourse end-of-life notice
Ubuntu 19.10 2020-07-17 vendor source ↗ vendor adapter ubuntu: the release team's list of releases publishes eol "2020-07-17", upstream "2020-07-06" (read twice, 2026-09-07); confirmed by the ubuntu-announce / Discourse end-of-life notice
Ruby 3.2 2026-04-01 vendor source ↗ Official branch page lists 3.2 EOL 2026-04-01; upstream shows 2026-03-31.
Rust 1.93 2026-03-05 vendor source ↗ Rust supports only the latest stable; 1.94.0 shipped 2026-03-05, ending 1.93. Upstream shows 2026-03-06.
Magento 2.4.6 2026-08-11 vendor source ↗ Two Adobe tracks reconciled 2026-07-26: eol = Magento Open Source security-maintenance end (upstream's OSS-policy-PDF dates preserved for 2.4.4/2.4.5), extendedSupport = Adobe Commerce end of extended support per the current lifecycle table (verified verbatim). 2.4.6+ standard/OSS ends align across editions per Adobe's table and multiple trackers. | extendedSupport corrected 2027-08-30 -> 2027-08-31 on 2026-09-07 from Adobe's End of support dates table (End of extended support column; docs source help/_includes/templated/release/end-of-support-dates.md).
Magento 2.4.7 2027-05-31 vendor source ↗ Two Adobe tracks reconciled 2026-07-26: eol = Magento Open Source security-maintenance end (upstream's OSS-policy-PDF dates preserved for 2.4.4/2.4.5), extendedSupport = Adobe Commerce end of extended support per the current lifecycle table (verified verbatim). 2.4.6+ standard/OSS ends align across editions per Adobe's table and multiple trackers.
Magento 2.4.8 2028-05-31 vendor source ↗ Two Adobe tracks reconciled 2026-07-26: eol = Magento Open Source security-maintenance end (upstream's OSS-policy-PDF dates preserved for 2.4.4/2.4.5), extendedSupport = Adobe Commerce end of extended support per the current lifecycle table (verified verbatim). 2.4.6+ standard/OSS ends align across editions per Adobe's table and multiple trackers. Extended TBD for 2.4.8/2.4.9. | 2026-10-06 extendedSupport false: Adobe lifecycle policy prints 2.4.8 end of extended support TBD; upstream served 2028-05-31 (the standard support end) as the extended end. Retire when Adobe prints the date (sentinel adobe-commerce-lifecycle-table).
Magento 2.4.9 2029-05-31 vendor source ↗ Two Adobe tracks reconciled 2026-07-26: eol = Magento Open Source security-maintenance end (upstream's OSS-policy-PDF dates preserved for 2.4.4/2.4.5), extendedSupport = Adobe Commerce end of extended support per the current lifecycle table (verified verbatim). 2.4.6+ standard/OSS ends align across editions per Adobe's table and multiple trackers. Extended TBD for 2.4.8/2.4.9.
Jenkins 2.555 2026-07-09 vendor source ↗ Jenkins LTS lines end when the successor BASELINE ships: jenkins-2.568.1 tag date is 2026-07-09, and every prior row in upstream jenkins.md uses the successor .1 date (2.541 eol = 2.555.1 Apr 15). Upstream PR #10680 (merged 2026-08-06) set 2.555 eol to 2026-06-10 — the 2.568 WEEKLY release date — breaking that precedent and predating 2.555.3 (Jun 8). Keep 2026-07-09 until upstream reconciles.
Jenkins 2.580 TBD (vendor has not confirmed a date) vendor source ↗ New Jenkins LTS line. jenkins.io LTS changelog: '2.580.1 September 30, 2026' (GitHub release jenkins-2.580.1 published 2026-09-30T11:24Z); jenkins.io weekly changelog: '2.580 September 2, 2026' (security release; GitHub release jenkins-2.580 published 2026-09-02, tag created 2026-08-31). Read twice 2026-10-09. Same shape as upstream's 2.568 row (releaseDate = baseline weekly, lts = .1 day, eol false while current). Upstream endoflife.date tops out at 2.568 (its weekly line '2' already shows 2.585). Retire when upstream adds 2.580; upstream may date releaseDate from the git tag (2026-08-31).
Jenkins 2.568 2026-09-30 vendor source ↗ Jenkins LTS lines end when the successor baseline ships: 2.580.1 released 2026-09-30 (jenkins.io LTS changelog and GitHub release jenkins-2.580.1, read twice 2026-10-09), and no 2.568.4 exists (2.568.3 is the last, 2026-08-31). Same rule as the existing jenkins 2.555 override (eol = successor .1 day, 2.568.1). Upstream still serves 2.568 eol false because it has not added 2.580. Retire when upstream sets it.
Jenkins 2.462 2024-10-30 vendor source ↗ Jenkins LTS lines end when the successor .1 ships (the rule of the existing jenkins 2.555 and 2.568 overrides and of every other upstream row: 2.541 eol = 2.555.1 day, 2.528 eol = 2.541.1 day). jenkins.io LTS changelog, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical): '2.479.1 October 30, 2024'; GitHub release jenkins-2.479.1 published 2024-10-30T14:11Z. Upstream serves 2.462 eol 2024-10-02, which is the GitHub publish timestamp shared by the 2.462.3 and 2.479 (weekly) release entries (both 2024-10-02T13:47Z, a bulk publish), not a Jenkins release day; 2.462.3 itself shipped 2024-09-19. Retire when upstream serves 2024-10-30.
Debian 9 2022-06-30 vendor source ↗ vendor adapter debian: vendor publishes extendedSupport "2022-06-30", upstream "2022-07-01" (read twice, 2026-09-06) | re-keyed 2026-09-07 to eol (upstream 0d36332: LTS end is now eol; upstream carries 2022-07-01).
Debian 12 — vendor source ↗ Debian's wiki and the dated end-of-support announcement both say 2026-07-12; only debian.org/releases/ (which upstream follows) still says 07-11. Vendor majority wins. Weekly verification sweep 2026-08-24. | re-keyed 2026-09-07 to support (upstream 0d36332: regular security end is now support; upstream carries 2026-07-11).
Node.js 4 — vendor source ↗ vendor adapter nodejs: vendor publishes releaseDate "2015-09-08", upstream "2015-09-09" (read twice, 2026-09-05) | vendor adapter nodejs: vendor publishes lts "2015-10-12", upstream "2015-10-01" (read twice, 2026-09-05)
Node.js 5 — vendor source ↗ vendor adapter nodejs: vendor publishes releaseDate "2015-10-29", upstream "2015-10-30" (read twice, 2026-09-05) | vendor adapter nodejs: vendor publishes support "2016-04-30", upstream "2016-06-30" (read twice, 2026-09-05)
Node.js 7 — vendor source ↗ vendor adapter nodejs: vendor publishes support "2017-04-30", upstream "2017-06-30" (read twice, 2026-09-05)
Node.js 9 — vendor source ↗ vendor adapter nodejs: vendor publishes releaseDate "2017-10-01", upstream "2017-10-31" (read twice, 2026-09-05) | vendor adapter nodejs: vendor publishes support "2018-04-01", upstream "2018-06-30" (read twice, 2026-09-05)
Node.js 11 2019-06-01 vendor source ↗ vendor adapter nodejs: vendor publishes support "2019-04-22", upstream "2019-04-01" (read twice, 2026-09-05) | vendor adapter nodejs: vendor publishes eol "2019-06-01", upstream "2019-06-30" (read twice, 2026-09-05)
Node.js 12 — vendor source ↗ Node.js Release WG schedule.json (read 2026-09-05): v12 maintenance started 2020-11-30 (the LTS phase was extended). Upstream endoflife.date has 2020-10-20.
Node.js 26 — vendor source ↗ Node.js Release WG schedule.json (read 2026-09-05): v26 maintenance starts 2027-10-20. Upstream endoflife.date has 2027-10-27, one week late.
.NET 1.1 — vendor source ↗ vendor adapter dotnet: vendor publishes lts true, upstream false (read twice, 2026-09-05)
.NET 1.0 — vendor source ↗ vendor adapter dotnet: vendor publishes lts true, upstream false (read twice, 2026-09-05)
Kubernetes 1.28 2024-10-22 vendor source ↗ vendor adapter kubernetes: vendor publishes eol "2024-10-22", upstream "2024-10-28" (read twice, 2026-09-05)
Kubernetes 1.27 2024-07-16 vendor source ↗ vendor adapter kubernetes: vendor publishes eol "2024-07-16", upstream "2024-06-28" (read twice, 2026-09-05)
Kubernetes 1.25 2023-10-28 vendor source ↗ vendor adapter kubernetes: vendor publishes eol "2023-10-28", upstream "2023-10-27" (read twice, 2026-09-05)
Kubernetes 1.22 2022-12-08 vendor source ↗ vendor adapter kubernetes: vendor publishes eol "2022-12-08", upstream "2022-10-28" (read twice, 2026-09-05)
Kubernetes 1.17 2021-01-13 vendor source ↗ vendor adapter kubernetes: vendor publishes eol "2021-01-13", upstream "2020-12-25" (read twice, 2026-09-05)
Kubernetes 1.16 2020-09-02 vendor source ↗ vendor adapter kubernetes: vendor publishes eol "2020-09-02", upstream "2020-08-04" (read twice, 2026-09-05)
Kubernetes 1.26 — vendor source ↗ vendor adapter kubernetes: vendor publishes releaseDate "2022-12-09", upstream "2022-12-08" (read twice, 2026-09-08); the release team schedule file lists v1.26.0 released Friday 9th December 2022
PHP 5.4 2015-09-03 vendor source ↗ vendor adapter php: vendor publishes eol "2015-09-03", upstream "2015-09-14" (read twice, 2026-09-05)
Spring Framework 4.3 — vendor source ↗ api.spring.io generations commercialSupportEndDate for 4.3.x is 2020-12-31 (VMware/Broadcom commercial support); upstream carries false (no commercial support). Applied by the director from the vendor adapter finding, value read from the API twice, 2026-09-05.
Spring Framework 5.0 — vendor source ↗ api.spring.io generations commercialSupportEndDate for 5.0.x is 2022-12-31 (VMware/Broadcom commercial support); upstream carries false (no commercial support). Applied by the director from the vendor adapter finding, value read from the API twice, 2026-09-05.
Spring Framework 7.0 — vendor source ↗ Day the 7.0.0 release was published: GitHub release v7.0.0 published 2025-11-13T10:33:28Z and the Maven Central spring-core 7.0.0 artifact (Last-Modified 13 Nov 2025 10:26:23 GMT) agree (read 2026-10-09). Upstream served 2025-11-30, the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. Same month-end trap as the spring-boot release-day overrides of 2026-09-25.
Spring Framework 6.2 — vendor source ↗ Day the 6.2.0 release was published: GitHub release v6.2.0 published 2024-11-14T16:46:47Z and the Maven Central spring-core 6.2.0 artifact (Last-Modified 14 Nov 2024 16:38:50 GMT) agree (read 2026-10-09). Upstream served 2024-11-30, the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. Same month-end trap as the spring-boot release-day overrides of 2026-09-25.
Spring Framework 6.1 — vendor source ↗ Day the 6.1.0 release was published: GitHub release v6.1.0 published 2023-11-16T14:54:56Z and the Maven Central spring-core 6.1.0 artifact (Last-Modified 16 Nov 2023 14:50:58 GMT) agree (read 2026-10-09). Upstream served 2023-11-30, the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. Same month-end trap as the spring-boot release-day overrides of 2026-09-25.
Spring Framework 6.0 — vendor source ↗ Day the 6.0.0 release was published: GitHub release v6.0.0 published 2022-11-16T11:09:35Z and the Maven Central spring-core 6.0.0 artifact (Last-Modified 16 Nov 2022 11:04:06 GMT) agree (read 2026-10-09). Upstream served 2022-11-30, the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. Same month-end trap as the spring-boot release-day overrides of 2026-09-25.
Spring Framework 5.1 — vendor source ↗ Day the 5.1.0 release shipped: Maven Central spring-core 5.1.0.RELEASE uploaded 2018-09-21 07:52 UTC (directory listing and the search API timestamp agree) and the spring.io post 'Spring Framework 5.1 goes GA' is dated September 21, 2018 (both read 2026-10-11). GitHub has no v5.1.0 release, so the adapter uses the Maven Central day for this line. Upstream served 2018-09-30, the month-end policy date from api.spring.io generations. Found by the spring-framework adapter's new release-day check on its first run.
Spring Framework 5.3 — vendor source ↗ Day the 5.3.0 release was published: GitHub release v5.3.0 published 2020-10-27T15:55:26Z and the Maven Central spring-core 5.3.0 artifact (Last-Modified 27 Oct 2020 15:47:40 GMT) agree (read 2026-10-09). Upstream served 2020-10-31, the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. Same month-end trap as the spring-boot release-day overrides of 2026-09-25.
Red Hat OpenShift 4.22 — vendor source ↗ vendor adapter red-hat-openshift: vendor publishes extendedSupport "2028-06-30", upstream false (read twice, 2026-09-06)
Red Hat OpenShift 4.21 — vendor source ↗ vendor adapter red-hat-openshift: vendor publishes releaseDate "2026-02-03", upstream "2025-10-21" (read twice, 2026-09-06)
Red Hat OpenShift 4.20 — vendor source ↗ vendor adapter red-hat-openshift: vendor publishes extendedSupport "2027-10-21", upstream false (read twice, 2026-09-06)
Red Hat OpenShift 4.6 — vendor source ↗ vendor adapter red-hat-openshift: vendor publishes releaseDate "2020-10-27", upstream "2020-11-09" (read twice, 2026-09-06)
Red Hat OpenShift 4.5 — vendor source ↗ vendor adapter red-hat-openshift: vendor publishes releaseDate "2020-07-13", upstream "2020-07-16" (read twice, 2026-09-06)
Red Hat OpenShift 4.4 — vendor source ↗ vendor adapter red-hat-openshift: vendor publishes releaseDate "2020-05-05", upstream "2020-05-18" (read twice, 2026-09-06)
Red Hat OpenShift 4.3 — vendor source ↗ vendor adapter red-hat-openshift: vendor publishes releaseDate "2020-01-23", upstream "2020-02-12" (read twice, 2026-09-06)
Red Hat OpenShift 4.2 — vendor source ↗ vendor adapter red-hat-openshift: vendor publishes releaseDate "2019-10-16", upstream "2019-10-29" (read twice, 2026-09-06)
Red Hat OpenShift 4.1 — vendor source ↗ vendor adapter red-hat-openshift: vendor publishes releaseDate "2019-06-04", upstream "2019-06-18" (read twice, 2026-09-06)
Oracle Database 10.2 — vendor source ↗ Oracle Lifetime Support Policy (Technology Products, effective Aug 7 2026): Oracle Database 10.2 Extended Support ended Jul 2013; upstream carried 2015-07-31. Applied by the director from the vendor adapter reading (PDF read twice), 2026-09-06.
Amazon EKS 1.35 — vendor source ↗ vendor adapter amazon-eks: vendor publishes releaseDate "2026-01-27", upstream "2026-01-28" (read twice, 2026-09-06)
Amazon EKS 1.34 — vendor source ↗ vendor adapter amazon-eks: vendor publishes releaseDate "2025-10-02", upstream "2025-10-06" (read twice, 2026-09-06)
Amazon EKS 1.33 — vendor source ↗ vendor adapter amazon-eks: vendor publishes releaseDate "2025-05-29", upstream "2025-05-28" (read twice, 2026-09-06)
Amazon EKS 1.32 — vendor source ↗ vendor adapter amazon-eks: vendor publishes releaseDate "2025-01-23", upstream "2025-01-25" (read twice, 2026-09-06)
Zabbix 7.4 TBD (vendor has not confirmed a date) vendor source ↗ vendor adapter zabbix: vendor publishes releaseDate "2025-07-01", upstream "2025-06-30" (read twice, 2026-09-06) | 2026-10-06 eol false: the Zabbix life cycle page prints End of Full Support "until 8.0 LTS" and End of Limited Support "Q1 2027" for 7.4, no day; upstream 2026-12-31 matches neither. Vendor floor rule. Retire when Zabbix prints the day or 8.0 LTS ships (sentinel zabbix-7-4-row).
Drupal 11.2 — vendor source ↗ vendor adapter drupal: vendor publishes releaseDate "2025-06-19", upstream "2025-06-18" (read twice, 2026-09-07) | vendor adapter drupal: vendor publishes eol "2026-07-01", upstream "2026-06-17" (read twice, 2026-09-07) | Evidence: release nodes on drupal.org (api-d7 + the release pages) show 11.2.0 created 19 Jun 2025 00:52 UTC and 10.5.0 19 Jun 2025 00:44 UTC (the pages display UTC); the announcement "Drupal 11.2.0 is now available" is published 2025-06-19T05:05Z and says 19 June 2025; upstream carries the US-time 18 June. End of security support: the schedule table row "Week of Jun 29, 2026 - Drupal 11.4.0 released. End of security support for 11.2.x and 10.5.x."; 11.4.0 released 1 Jul 2026 (release node); the 11.2.14 and 10.5.12 release pages (17 Jun 2026) say the branch "is expected to be end-of-life next week". Upstream carries the last patch day (17 Jun 2026). | eol retired 2026-09-07: upstream PR #10928 merged with 2026-07-01; releaseDate stays (upstream derives it from the git tag, 2025-06-18).
Drupal 10.5 — vendor source ↗ vendor adapter drupal: vendor publishes releaseDate "2025-06-19", upstream "2025-06-18" (read twice, 2026-09-07) | vendor adapter drupal: vendor publishes eol "2026-07-01", upstream "2026-06-17" (read twice, 2026-09-07) | Evidence: release nodes on drupal.org (api-d7 + the release pages) show 11.2.0 created 19 Jun 2025 00:52 UTC and 10.5.0 19 Jun 2025 00:44 UTC (the pages display UTC); the announcement "Drupal 11.2.0 is now available" is published 2025-06-19T05:05Z and says 19 June 2025; upstream carries the US-time 18 June. End of security support: the schedule table row "Week of Jun 29, 2026 - Drupal 11.4.0 released. End of security support for 11.2.x and 10.5.x."; 11.4.0 released 1 Jul 2026 (release node); the 11.2.14 and 10.5.12 release pages (17 Jun 2026) say the branch "is expected to be end-of-life next week". Upstream carries the last patch day (17 Jun 2026). | eol retired 2026-09-07: upstream PR #10928 merged with 2026-07-01; releaseDate stays (upstream derives it from the git tag, 2025-06-18).
Drupal 11.4 TBD (vendor has not confirmed a date) vendor source ↗ 2026-10-11 (audit Q4): the 11.4.9 release page (created 9 Oct 2026) says 'Drupal 11.4.x will receive security coverage until June 2027.' (month only). The release schedule lists 'Bugfix release window for Drupal 11.4.x' each month and 'Week of Dec 07, 2026 (UTC) Drupal 12.0.0 and 11.5.0 released. End of security support for 11.3.x and 10.6.x.' and names no day for either 11.4 end. Upstream serves support 2027-01-01 and eol 2027-07-07 (outside the vendor's month). Vendor floor rule: a month-only end is not served as a day, so support and eol are false (not announced) until drupal.org names the day (the schedule row for the 11.6.0/12.1.0 release; the drupal adapter reads it). Read twice 2026-10-11 (WebFetch and the built-in browser). Guarded by the month-precision exact rule for drupal and golden cases.
Drupal 11.3 TBD (vendor has not confirmed a date) vendor source ↗ 2026-10-11 (audit Q4): the 11.3.18 release page (created 28 Sep 2026) says 'Drupal 11.3.x will receive security coverage until December 2026.' and the schedule says 'Week of Dec 07, 2026 (UTC) Drupal 12.0.0 and 11.5.0 released. End of security support for 11.3.x and 10.6.x.' Security support ends on the 11.5.0 release day, which drupal.org has not named; upstream serves 2026-12-16, after that week. eol false until 11.5.0 ships: the drupal adapter then reports the exact day from the release API (until then it reports month 2026-12 and the runner prints this override as decided, a reminder to retire it). Read twice 2026-10-11 (WebFetch and the built-in browser). 10.6 is in the same schedule row and was not changed here.
GitLab 16.0 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2023-05-22", upstream "2023-05-18" (read twice, 2026-09-07)
GitLab 16.1 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2023-06-22", upstream "2023-06-21" (read twice, 2026-09-07)
GitLab 16.2 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2023-07-22", upstream "2023-07-21" (read twice, 2026-09-07)
GitLab 16.3 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2023-08-22", upstream "2023-08-21" (read twice, 2026-09-07)
GitLab 16.4 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2023-09-22", upstream "2023-09-21" (read twice, 2026-09-07)
GitLab 16.5 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2023-10-22", upstream "2023-10-20" (read twice, 2026-09-07)
GitLab 16.6 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2023-11-16", upstream "2023-11-15" (read twice, 2026-09-07)
GitLab 16.7 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2023-12-21", upstream "2023-12-20" (read twice, 2026-09-07)
GitLab 16.8 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-01-18", upstream "2024-01-17" (read twice, 2026-09-07)
GitLab 16.9 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-02-15", upstream "2024-02-14" (read twice, 2026-09-07)
GitLab 16.10 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-03-21", upstream "2024-03-20" (read twice, 2026-09-07)
GitLab 16.11 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-04-18", upstream "2024-04-17" (read twice, 2026-09-07)
GitLab 17.0 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-05-16", upstream "2024-05-15" (read twice, 2026-09-07)
GitLab 17.1 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-06-20", upstream "2024-06-19" (read twice, 2026-09-07)
GitLab 17.2 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-07-18", upstream "2024-07-17" (read twice, 2026-09-07)
GitLab 17.3 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-08-15", upstream "2024-08-14" (read twice, 2026-09-07)
GitLab 17.4 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-09-19", upstream "2024-09-18" (read twice, 2026-09-07)
GitLab 17.5 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-10-17", upstream "2024-10-16" (read twice, 2026-09-07)
GitLab 17.6 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-11-21", upstream "2024-11-20" (read twice, 2026-09-07)
GitLab 17.7 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2024-12-19", upstream "2024-12-18" (read twice, 2026-09-07)
GitLab 17.8 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2025-01-16", upstream "2025-01-15" (read twice, 2026-09-07)
GitLab 17.9 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2025-02-20", upstream "2025-02-19" (read twice, 2026-09-07)
GitLab 17.10 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2025-03-20", upstream "2025-03-19" (read twice, 2026-09-07)
GitLab 17.11 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2025-04-17", upstream "2025-04-16" (read twice, 2026-09-07)
GitLab 18.0 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2025-05-15", upstream "2025-05-14" (read twice, 2026-09-07)
GitLab 18.1 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2025-06-19", upstream "2025-06-18" (read twice, 2026-09-07)
GitLab 18.2 — vendor source ↗ vendor adapter gitlab: vendor publishes releaseDate "2025-07-17", upstream "2025-07-16" (read twice, 2026-09-07)
Windows 10-1803-e — vendor source ↗ vendor adapter windows: vendor publishes support "2021-05-11", upstream "2020-05-11" (read twice, 2026-09-07)
Windows 11-26h2-w 2028-10-10 vendor source ↗ Decided 2026-10-01 from two Microsoft pages that disagree by one day. The Windows 11 release information page lists 26H2 end of updates as 2028-10-10 for Home and Pro (a Patch Tuesday, the day servicing ends for every earlier release). The Learn lifecycle product page stores the retirement as 10/10/2028 06:59:59 UTC, which renders as October 9, 2028 (a Monday) in Pacific time, where the 25H2 row stores 10/13/2027 06:59:59 UTC for October 12, 2027. Upstream carries 2028-10-10. Served value kept; both pages read 2026-10-01.
Django 1.7 — vendor source ↗ vendor adapter django: vendor publishes releaseDate "2014-09-02", upstream "2014-09-03" (read twice, 2026-09-08); the Django 1.7 release notes are dated September 2, 2014
Angular 12 — vendor source ↗ vendor adapter angular: vendor publishes releaseDate "2021-05-12", upstream "2021-05-13" (read twice, 2026-09-08); @angular/core 12.0.0 was published to npm on 2021-05-12, the day of the v12 announcement
Internet Explorer 11 2022-06-15 vendor source ↗ Microsoft: the IE 11 desktop application ended support on June 15, 2022 (Windows 10 semi-annual channel). endoflife.date carries 2022-06-14. Found 2026-09-08 when Lansweeper Lens reported June 15 on our own site and we reported June 14.
Apache Kafka 4.3 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2026-05-22", upstream "2026-05-20" (read twice, 2026-09-10) | 2026-10-11 extendedSupport false (audit Q9): Apache Kafka publishes no extended support. Its EOL policy (cwiki Time Based Release Plan, 'What Is Our EOL Policy?') says 'We will also attempt, as a community to do bugfix releases as needed for the last 3 releases.' Upstream's date here is Confluent's, from the Confluent Platform supported versions table (endoflife.date column 'Confluent Community software End of Support'; for 4.x the value equals Confluent Enterprise Standard End of Support), e.g. '8.3.x | 4.3.x | June 17, 2026 | June 17, 2027 | June 17, 2028 | June 17, 2029' and '7.8.x | 3.8.x | December 2, 2024 | December 2, 2026 | December 2, 2026 | December 2, 2027'. It was shown unattributed as Kafka extended support (3.8 as patches still flowing). Confluent's support for Kafka is on /confluent-platform. Read twice 2026-10-11 (WebFetch and browser for the Apache policy; curl and browser for the Confluent table).
Apache Kafka 3.8 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2024-07-29", upstream "2024-07-26" (read twice, 2026-09-10) | 2026-10-11 extendedSupport false (audit Q9): Apache Kafka publishes no extended support. Its EOL policy (cwiki Time Based Release Plan, 'What Is Our EOL Policy?') says 'We will also attempt, as a community to do bugfix releases as needed for the last 3 releases.' Upstream's date here is Confluent's, from the Confluent Platform supported versions table (endoflife.date column 'Confluent Community software End of Support'; for 4.x the value equals Confluent Enterprise Standard End of Support), e.g. '8.3.x | 4.3.x | June 17, 2026 | June 17, 2027 | June 17, 2028 | June 17, 2029' and '7.8.x | 3.8.x | December 2, 2024 | December 2, 2026 | December 2, 2026 | December 2, 2027'. It was shown unattributed as Kafka extended support (3.8 as patches still flowing). Confluent's support for Kafka is on /confluent-platform. Read twice 2026-10-11 (WebFetch and browser for the Apache policy; curl and browser for the Confluent table).
Apache Kafka 3.7 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2024-02-27", upstream "2024-02-26" (read twice, 2026-09-10)
Apache Kafka 3.6 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2023-10-10", upstream "2023-10-03" (read twice, 2026-09-10)
Apache Kafka 3.5 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2023-06-15", upstream "2023-06-13" (read twice, 2026-09-10)
Apache Kafka 3.4 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2023-02-07", upstream "2023-02-06" (read twice, 2026-09-10)
Apache Kafka 3.2 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2022-05-17", upstream "2022-05-09" (read twice, 2026-09-10)
Apache Kafka 3.1 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2022-01-24", upstream "2022-01-21" (read twice, 2026-09-10)
Apache Kafka 3.0 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2021-09-21", upstream "2021-09-20" (read twice, 2026-09-10)
Apache Kafka 2.8 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2021-04-19", upstream "2021-04-18" (read twice, 2026-09-10)
Apache Kafka 2.7 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2020-12-21", upstream "2020-12-19" (read twice, 2026-09-10)
Apache Kafka 2.5 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2020-04-15", upstream "2020-04-14" (read twice, 2026-09-10)
Apache Kafka 2.4 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2019-12-16", upstream "2019-12-14" (read twice, 2026-09-10)
Apache Kafka 2.3 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2019-06-25", upstream "2019-06-24" (read twice, 2026-09-10)
Apache Kafka 2.0 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2018-07-30", upstream "2018-07-28" (read twice, 2026-09-10)
Apache Kafka 1.0 — vendor source ↗ vendor adapter apache-kafka: vendor publishes releaseDate "2017-11-01", upstream "2017-10-31" (read twice, 2026-09-10)
Apache Kafka 4.2 — vendor source ↗ 2026-10-11 extendedSupport false (audit Q9): Apache Kafka publishes no extended support. Its EOL policy (cwiki Time Based Release Plan, 'What Is Our EOL Policy?') says 'We will also attempt, as a community to do bugfix releases as needed for the last 3 releases.' Upstream's date here is Confluent's, from the Confluent Platform supported versions table (endoflife.date column 'Confluent Community software End of Support'; for 4.x the value equals Confluent Enterprise Standard End of Support), e.g. '8.3.x | 4.3.x | June 17, 2026 | June 17, 2027 | June 17, 2028 | June 17, 2029' and '7.8.x | 3.8.x | December 2, 2024 | December 2, 2026 | December 2, 2026 | December 2, 2027'. It was shown unattributed as Kafka extended support (3.8 as patches still flowing). Confluent's support for Kafka is on /confluent-platform. Read twice 2026-10-11 (WebFetch and browser for the Apache policy; curl and browser for the Confluent table).
Apache Kafka 4.1 — vendor source ↗ 2026-10-11 extendedSupport false (audit Q9): Apache Kafka publishes no extended support. Its EOL policy (cwiki Time Based Release Plan, 'What Is Our EOL Policy?') says 'We will also attempt, as a community to do bugfix releases as needed for the last 3 releases.' Upstream's date here is Confluent's, from the Confluent Platform supported versions table (endoflife.date column 'Confluent Community software End of Support'; for 4.x the value equals Confluent Enterprise Standard End of Support), e.g. '8.3.x | 4.3.x | June 17, 2026 | June 17, 2027 | June 17, 2028 | June 17, 2029' and '7.8.x | 3.8.x | December 2, 2024 | December 2, 2026 | December 2, 2026 | December 2, 2027'. It was shown unattributed as Kafka extended support (3.8 as patches still flowing). Confluent's support for Kafka is on /confluent-platform. Read twice 2026-10-11 (WebFetch and browser for the Apache policy; curl and browser for the Confluent table).
Apache Kafka 4.0 — vendor source ↗ 2026-10-11 extendedSupport false (audit Q9): Apache Kafka publishes no extended support. Its EOL policy (cwiki Time Based Release Plan, 'What Is Our EOL Policy?') says 'We will also attempt, as a community to do bugfix releases as needed for the last 3 releases.' Upstream's date here is Confluent's, from the Confluent Platform supported versions table (endoflife.date column 'Confluent Community software End of Support'; for 4.x the value equals Confluent Enterprise Standard End of Support), e.g. '8.3.x | 4.3.x | June 17, 2026 | June 17, 2027 | June 17, 2028 | June 17, 2029' and '7.8.x | 3.8.x | December 2, 2024 | December 2, 2026 | December 2, 2026 | December 2, 2027'. It was shown unattributed as Kafka extended support (3.8 as patches still flowing). Confluent's support for Kafka is on /confluent-platform. Read twice 2026-10-11 (WebFetch and browser for the Apache policy; curl and browser for the Confluent table).
Apache Kafka 3.9 — vendor source ↗ 2026-10-11 extendedSupport false (audit Q9): Apache Kafka publishes no extended support. Its EOL policy (cwiki Time Based Release Plan, 'What Is Our EOL Policy?') says 'We will also attempt, as a community to do bugfix releases as needed for the last 3 releases.' Upstream's date here is Confluent's, from the Confluent Platform supported versions table (endoflife.date column 'Confluent Community software End of Support'; for 4.x the value equals Confluent Enterprise Standard End of Support), e.g. '8.3.x | 4.3.x | June 17, 2026 | June 17, 2027 | June 17, 2028 | June 17, 2029' and '7.8.x | 3.8.x | December 2, 2024 | December 2, 2026 | December 2, 2026 | December 2, 2027'. It was shown unattributed as Kafka extended support (3.8 as patches still flowing). Confluent's support for Kafka is on /confluent-platform. Read twice 2026-10-11 (WebFetch and browser for the Apache policy; curl and browser for the Confluent table).
AWS Lambda nodejs4.3-edge 2019-04-30 vendor source ↗ vendor adapter aws-lambda: vendor publishes eol "2019-04-30", upstream "2020-04-30" (read twice, 2026-09-10)
Firefox 150 2026-05-19 vendor source ↗ vendor adapter firefox: vendor publishes eol "2026-05-19", upstream "2026-05-18" (read twice, 2026-09-10)
Firefox 151 — vendor source ↗ vendor adapter firefox: vendor publishes releaseDate "2026-05-19", upstream "2026-05-18" (read twice, 2026-09-10)
Horizon 8.2312 2027-04-23 vendor source ↗ vendor adapter horizon: vendor publishes eol "2027-04-23", upstream "2027-01-23" (read twice, 2026-09-10)
NGINX 1.27 — vendor source ↗ vendor adapter nginx: vendor publishes releaseDate "2024-05-29", upstream "2024-05-28" (read twice, 2026-09-10)
NGINX 1.16 2020-04-21 vendor source ↗ vendor adapter nginx: vendor publishes eol "2020-04-21", upstream "2020-04-20" (read twice, 2026-09-10)
Rocket.Chat 8.7 2027-02-28 vendor source ↗ Rocket.Chat Version Durability matrix read 2026-10-09: 8.7 (8.7.1) Aug 2026 to Feb 2027, with the page rule "EOL is the last day of the month when support for a version officially ends", so 2027-02-28. Upstream serves 2027-01-31, a month early. Same convention as 8.5.
Rocket.Chat 8.8 2027-03-31 vendor source ↗ Rocket.Chat Version Durability matrix read 2026-10-09: 8.8 (8.8.1) Sep 2026 to Mar 2027, with the page rule "EOL is the last day of the month when support for a version officially ends", so 2027-03-31. Upstream serves 2027-03-01, the first day of the month.
Rocket.Chat 8.5 2027-06-30 vendor source ↗ vendor adapter rocket-chat: the Version Durability matrix states End of Life "2027-06" for 8.5 LTS (read 2026-09-09 and 2026-09-10, identical), upstream serves 2027-07-31. Month-precision vendor date applied as the end-of-month day per site convention. LTS line: twelve months from the Jun 2026 release. Rocket.Chat's release-notes page carries day-level Support Window lines but with errors on its own page (8.7.0 "February 31, 2027", 8.6.0 "January 31, 2026"), so the matrix is the statement used.
Rocket.Chat 7.10 2026-09-30 vendor source ↗ vendor adapter rocket-chat: the Version Durability matrix states End of Life "2026-09" for 7.10 LTS (read 2026-09-09 and 2026-09-10, identical), upstream serves 2026-07-10. Month-precision vendor date applied as the end-of-month day per site convention. LTS line: twelve months from the Sep 2025 release; upstream's July day matches no vendor statement. Rocket.Chat's release-notes page carries day-level Support Window lines but with errors on its own page (8.7.0 "February 31, 2027", 8.6.0 "January 31, 2026"), so the matrix is the statement used.
Rocket.Chat 6.6 2024-08-31 vendor source ↗ vendor adapter rocket-chat: the Version Durability matrix states End of Life "2024-08" for 6.6 (read 2026-09-09 and 2026-09-10, identical), upstream serves 2024-11-22. Month-precision vendor date applied as the end-of-month day per site convention. Upstream ends every 6.x line at the 7.0 release in Nov 2024; the matrix states the six-month window per line. Rocket.Chat's release-notes page carries day-level Support Window lines but with errors on its own page (8.7.0 "February 31, 2027", 8.6.0 "January 31, 2026"), so the matrix is the statement used.
Rocket.Chat 6.5 2024-06-30 vendor source ↗ vendor adapter rocket-chat: the Version Durability matrix states End of Life "2024-06" for 6.5 (read 2026-09-09 and 2026-09-10, identical), upstream serves 2024-11-22. Month-precision vendor date applied as the end-of-month day per site convention. Upstream ends every 6.x line at the 7.0 release in Nov 2024; the matrix states the six-month window per line. Rocket.Chat's release-notes page carries day-level Support Window lines but with errors on its own page (8.7.0 "February 31, 2027", 8.6.0 "January 31, 2026"), so the matrix is the statement used.
Rocket.Chat 6.3 2024-02-29 vendor source ↗ vendor adapter rocket-chat: the Version Durability matrix states End of Life "2024-02" for 6.3 (read 2026-09-09 and 2026-09-10, identical), upstream serves 2024-11-23. Month-precision vendor date applied as the end-of-month day per site convention. Upstream ends every 6.x line at the 7.0 release in Nov 2024; the matrix states the six-month window per line. Rocket.Chat's release-notes page carries day-level Support Window lines but with errors on its own page (8.7.0 "February 31, 2027", 8.6.0 "January 31, 2026"), so the matrix is the statement used.
Rocket.Chat 4.1 2022-04-30 vendor source ↗ vendor adapter rocket-chat: the Version Durability matrix states End of Life "2022-04" for 4.1 (read 2026-09-09 and 2026-09-10, identical), upstream serves 2022-06-02. Month-precision vendor date applied as the end-of-month day per site convention. Rocket.Chat's release-notes page carries day-level Support Window lines but with errors on its own page (8.7.0 "February 31, 2027", 8.6.0 "January 31, 2026"), so the matrix is the statement used.
Rocket.Chat 3.18 2022-02-28 vendor source ↗ vendor adapter rocket-chat: the Version Durability matrix states End of Life "2022-02" for 3.18 (read 2026-09-09 and 2026-09-10, identical), upstream serves 2022-05-30. Month-precision vendor date applied as the end-of-month day per site convention. Rocket.Chat's release-notes page carries day-level Support Window lines but with errors on its own page (8.7.0 "February 31, 2027", 8.6.0 "January 31, 2026"), so the matrix is the statement used.
Rocket.Chat 8.0 2026-07-31 vendor source ↗ Rocket.Chat Version Durability matrix read twice 2026-10-09; page rule: "EOL is the last day of the month when support for a version officially ends." 8.0 end of life Jul 2026 = 2026-07-31.
Rocket.Chat 7.13 2026-06-30 vendor source ↗ Rocket.Chat Version Durability matrix read twice 2026-10-09; page rule: "EOL is the last day of the month when support for a version officially ends." 7.13 end of life Jun 2026 = 2026-06-30.
Rocket.Chat 7.11 2026-04-30 vendor source ↗ Rocket.Chat Version Durability matrix read twice 2026-10-09; page rule: "EOL is the last day of the month when support for a version officially ends." 7.11 end of life Apr 2026 = 2026-04-30.
Rocket.Chat 7.4 2025-09-30 vendor source ↗ Rocket.Chat Version Durability matrix read twice 2026-10-09; page rule: "EOL is the last day of the month when support for a version officially ends." 7.4 end of life Sep 2025 = 2025-09-30.
Rocket.Chat 7.0 2025-05-31 vendor source ↗ Rocket.Chat Version Durability matrix read twice 2026-10-09; page rule: "EOL is the last day of the month when support for a version officially ends." 7.0 end of life May 2025 = 2025-05-31.
Kirby 5 2028-06-24 vendor source ↗ vendor adapter kirby: vendor publishes eol "2028-06-24", upstream false (read twice, 2026-09-11)
Kirby 3.10 2025-12-01 vendor source ↗ vendor adapter kirby: vendor publishes eol "2025-12-01", upstream "2025-11-27" (read twice, 2026-09-11)
Kirby 3.9 2025-12-01 vendor source ↗ vendor adapter kirby: vendor publishes eol "2025-12-01", upstream "2025-11-27" (read twice, 2026-09-11)
Kirby 3.8 2024-12-02 vendor source ↗ vendor adapter kirby: vendor publishes eol "2024-12-02", upstream "2025-01-16" (read twice, 2026-09-11)
Kirby 3.7 2024-06-27 vendor source ↗ vendor adapter kirby: vendor publishes eol "2024-06-27", upstream "2024-10-05" (read twice, 2026-09-11)
Kirby 3.6 2024-06-27 vendor source ↗ vendor adapter kirby: vendor publishes eol "2024-06-27", upstream "2024-06-26" (read twice, 2026-09-11)
Kirby 3.5 2023-11-16 vendor source ↗ vendor adapter kirby: vendor publishes eol "2023-11-16", upstream "2023-11-15" (read twice, 2026-09-11)
Adobe ColdFusion 11 2019-04-30 vendor source ↗ vendor adapter coldfusion: vendor publishes eol "2019-04-30", upstream "2019-06-11" (read twice, 2026-09-19)
Adobe ColdFusion 2016 2021-02-17 vendor source ↗ vendor adapter coldfusion: vendor publishes eol "2021-02-17", upstream "2021-03-22" (read twice, 2026-09-19)
Adobe ColdFusion 2018 2023-07-13 vendor source ↗ vendor adapter coldfusion: vendor publishes eol "2023-07-13", upstream "2023-07-19" (read twice, 2026-09-19)
Adobe ColdFusion 2021 2025-11-10 vendor source ↗ vendor adapter coldfusion: vendor publishes eol "2025-11-10", upstream "2025-12-09" (read twice, 2026-09-19)
Adobe ColdFusion 2023 — vendor source ↗ vendor adapter coldfusion: vendor publishes releaseDate "2023-05-17", upstream "2022-05-16" (read twice, 2026-09-19)
Adobe ColdFusion 2025 2030-02-26 vendor source ↗ vendor adapter coldfusion: vendor publishes eol "2030-02-26", upstream "2030-04-08" (read twice, 2026-09-19) | 2026-10-11 extendedSupport false (audit Q5): Adobe's products and technical support periods matrix row reads 'ColdFusion | 2025 | | 02/25/2025 | 02/26/2030 | N/A' under 'General availability | End of core support | End of extended support'. Adobe publishes no extended support phase for ColdFusion 2025; upstream serves 2031-04-08, which the site labelled Adobe extended support. Read twice 2026-10-11 (built-in browser table read; raw page via the coldfusion adapter with a browser UA, which now records N/A as extendedSupport false).
Checkmk 2.4 — vendor source ↗ vendor publishes End of active maintenance 2026-10-28 for 2.4.0 in its user guide version table; upstream serves no support date for this cycle (read three times 2026-09-19: browser fetch, raw page, vendor adapter checkmk)
Checkmk 2.3 — vendor source ↗ vendor publishes End of active maintenance 2025-11-06 for 2.3.0 in its user guide version table; upstream serves no support date for this cycle (read three times 2026-09-19: browser fetch, raw page, vendor adapter checkmk)
Confluence 7.13 — vendor source ↗ Atlassian's Confluence 7.13 release notes are dated 17 August 2021 and print Released on 17 August 2021 for 7.13.0; upstream serves 2021-08-15. Atlassian's end of life for 7.13 (2023-08-17) is two years after the vendor's day, which agrees with its two-year policy (read twice 2026-09-20: browser fetch and raw page; sentinel confluence-713-released re-checks the page every build)
Confluence 11.0 — vendor source ↗ Upstream endoflife.date added confluence 11.0 on 2026-10-12 (eol 2028-10-08, latest 11.0.0, lts false agree with the vendor pages, so the _add entry and those fields were retired 2026-10-13). Upstream serves releaseDate and latestReleaseDate 2026-10-09; Atlassian's Confluence 11.0 release notes are dated '8 October 2026' and print 'Issues resolved in 11.0.0 Released on 08 October 2026' (read twice: 2026-10-09 raw page and built-in browser, 2026-10-13 fetched again). Upstream is a day late here, the Atlassian one-day pattern of the 10-11 audit; the confluence adapter reads the vendor day. | 2026-10-16: latestReleaseDate retired, upstream now serves 2026-10-08; releaseDate kept (upstream still 2026-10-09).
Confluence 9.2 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 9.2 print "Issues resolved in 9.2.0 Released on 10 December 2024"; upstream serves 2024-12-09. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Confluence 8.9 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 8.9 print "Issues resolved in 8.9.0 Released on 02 April 2024"; upstream serves 2024-04-01. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Confluence 8.0 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 8.0 print "Issues resolved in 8.0.0 Released on 29 November 2022"; upstream serves 2022-11-28. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Red Hat Satellite 6.17 2026-11-28 vendor source ↗ vendor adapter redhat-satellite: vendor publishes eol "2026-11-28", upstream "2026-11-30" (read twice, 2026-09-22)
Red Hat Satellite 6.14 2025-05-30 vendor source ↗ vendor adapter redhat-satellite: vendor publishes eol "2025-05-30", upstream "2025-05-31" (read twice, 2026-09-22)
Red Hat Satellite 6.16 — vendor source ↗ vendor adapter redhat-satellite: Red Hat publishes an Extended update support phase for 6.16 ending 2027-05-31 (start 2026-06-01); upstream has no extended support for 6.16 (read twice, 2026-09-22)
Red Hat Satellite 6.19 TBD (vendor has not confirmed a date) vendor source ↗ Red Hat Product Life Cycles API read 2026-10-07 for Red Hat Satellite Server 6.19: Full support 'Estimated Nov, 2026', Maintenance support 'Estimated Nov, 2027', Extended update support 'Estimated Nov, 2028' (date_format string, month only, flagged estimate). Upstream serves 2026-11-01 and 2027-11-01, the first of each month. Vendor floor rule: an estimated month is not served as a day. Retire when Red Hat prints a date (sentinel redhat-satellite-api-6-19).
Red Hat Satellite 6.18 TBD (vendor has not confirmed a date) vendor source ↗ Red Hat Product Life Cycles API read 2026-10-07 for Red Hat Satellite Server 6.18: Maintenance support 'Estimated May, 2027' (month only, estimate); Full support 2026-05-06 is a real date and stays. Upstream serves 2027-05-01. Retire when Red Hat prints a date (sentinel redhat-satellite-api-6-19).
Red Hat Ansible Automation Platform 2.7 2028-06-02 vendor source ↗ vendor adapter red-hat-ansible-automation-platform: Red Hat publishes 2.7 (GA 2026-06-02, Full support to 2027-06-02, Maintenance Support 1 to 2028-06-02, Maintenance support 2 to 2029-06-02); upstream does not carry 2.7 yet (read twice, 2026-09-22). Retire when upstream adds it.
Google Kubernetes Engine 1.32 2026-04-27 vendor source ↗ vendor adapter google-kubernetes-engine: vendor publishes eol "2026-04-27", upstream "2026-04-11" (read twice, 2026-09-22) Extended channel: Google publishes end of extended support 2027-02-11 for 1.32; upstream carries no extended support date (read twice, 2026-09-22).
Google Kubernetes Engine 1.33 2026-08-12 vendor source ↗ vendor adapter google-kubernetes-engine: vendor publishes eol "2026-08-12", upstream "2026-08-03" (read twice, 2026-09-22) Extended channel: Google publishes end of extended support 2027-06-12 for 1.33; upstream carries no extended support date (read twice, 2026-09-22).
Google Kubernetes Engine 1.34 2027-01-25 vendor source ↗ vendor adapter google-kubernetes-engine: vendor publishes eol "2027-01-25", upstream "2026-10-01" (read twice, 2026-09-22) Extended channel: Google publishes end of extended support 2027-11-25 for 1.34; upstream carries no extended support date (read twice, 2026-09-22).
Google Kubernetes Engine 1.30 — vendor source ↗ Extended channel: Google publishes end of extended support 2026-07-30 for 1.30; upstream carries no extended support date (read twice, 2026-09-22).
Google Kubernetes Engine 1.31 — vendor source ↗ Extended channel: Google publishes end of extended support 2026-10-22 for 1.31; upstream carries no extended support date (read twice, 2026-09-22).
Google Kubernetes Engine 1.35 — vendor source ↗ Extended channel: Google publishes end of extended support 2028-02-11 for 1.35; upstream carries no extended support date (read twice, 2026-09-22).
Google Kubernetes Engine 1.36 — vendor source ↗ Extended channel: Google publishes end of extended support 2028-06-09 for 1.36; upstream carries no extended support date (read twice, 2026-09-22).
Istio 1.31 — vendor source ↗ vendor adapter istio: vendor publishes releaseDate "2026-08-27", upstream "2026-08-31" (read twice, 2026-09-23)
Istio 1.30 — vendor source ↗ vendor adapter istio: vendor publishes releaseDate "2026-05-14", upstream "2026-05-18" (read twice, 2026-09-23)
Istio 1.29 2026-10-12 vendor source ↗ vendor adapter istio: vendor publishes eol "2026-10-12", upstream "2026-10-31" (read twice, 2026-09-23)
Istio 1.18 — vendor source ↗ vendor adapter istio: vendor publishes releaseDate "2023-06-03", upstream "2023-06-07" (read twice, 2026-09-23)
Istio 1.14 — vendor source ↗ vendor adapter istio: vendor publishes releaseDate "2022-05-24", upstream "2022-06-01" (read twice, 2026-09-23)
Amazon Corretto 11 — vendor source ↗ AWS Corretto FAQ support calendar states GA Date March 15, 2019; upstream 2019-02-18 is a preview build date (read three times on 2026-09-24, identical; weekly verification sweep, approved by Scott 2026-09-24).
Amazon Corretto 17 — vendor source ↗ AWS Corretto FAQ support calendar states GA Date September 16, 2021; upstream 2021-08-24 is a preview build that predates the OpenJDK 17 GA (read three times on 2026-09-24, identical; weekly verification sweep, approved by Scott 2026-09-24).
Amazon Corretto 21 — vendor source ↗ AWS Corretto FAQ support calendar states GA Date September 21, 2023; upstream 2023-08-21 is a preview build that predates the OpenJDK 21 GA (read three times on 2026-09-24, identical; weekly verification sweep, approved by Scott 2026-09-24).
Amazon Corretto 25 — vendor source ↗ AWS Corretto FAQ support calendar states GA Date September 16, 2025; upstream 2025-09-17 (read three times on 2026-09-24, identical; weekly verification sweep, approved by Scott 2026-09-24).
Amazon Corretto 27 — vendor source ↗ AWS Corretto FAQ support calendar states GA Date September 15, 2026; upstream 2026-09-17 (read three times on 2026-09-24, identical; weekly verification sweep, approved by Scott 2026-09-24).
Claude (Anthropic) claude-fable-5-1 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-fable-5-1 as Active, Deprecated N/A, Tentative retirement date "Not sooner than September 1, 2027". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2027-09-01) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-mythos-5-1 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-mythos-5-1 as Active, Deprecated N/A, Tentative retirement date "Not sooner than September 1, 2027". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2027-09-01) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-fable-5 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-fable-5 as Active, Deprecated N/A, Tentative retirement date "Not sooner than June 9, 2027". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2027-06-09) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-mythos-5 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-mythos-5 as Active, Deprecated N/A, Tentative retirement date "Not sooner than June 9, 2027". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2027-06-09) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-sonnet-5-5 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-sonnet-5-5 as Active, Deprecated N/A, Tentative retirement date "Not sooner than September 28, 2027" (page read 2026-10-01). That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream added the model with the floor (2027-09-28) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced. Found by the vendor-adapter run on 2026-10-01, the first run in twelve days not masked by the ColdFusion fetch failure. Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-opus-5-5 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-opus-5-5 as Active, Deprecated N/A, Tentative retirement date "Not sooner than September 22, 2027". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2027-09-22) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-opus-5 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-opus-5 as Active, Deprecated N/A, Tentative retirement date "Not sooner than July 24, 2027". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2027-07-24) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-opus-4-8 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-opus-4-8 as Active, Deprecated N/A, Tentative retirement date "Not sooner than May 28, 2027". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2027-05-28) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-opus-4-7 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-opus-4-7 as Active, Deprecated N/A, Tentative retirement date "Not sooner than April 16, 2027". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2027-04-16) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-opus-4-6 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-opus-4-6 as Active, Deprecated N/A, Tentative retirement date "Not sooner than February 5, 2027". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2027-02-05) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-opus-4-5-20251101 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-opus-4-5-20251101 as Active, Deprecated N/A, Tentative retirement date "Not sooner than November 24, 2026". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2026-11-24) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-sonnet-5 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-sonnet-5 as Active, Deprecated N/A, Tentative retirement date "Not sooner than June 30, 2027". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2027-06-30) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-sonnet-4-6 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-sonnet-4-6 as Active, Deprecated N/A, Tentative retirement date "Not sooner than February 17, 2027". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2027-02-17) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-haiku-4-5-20251001 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-haiku-4-5-20251001 as Active, Deprecated N/A, Tentative retirement date "Not sooner than October 15, 2026". That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream serves the floor (2026-10-15) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced (Sonnet 4.5 was shown as end of life 2026-09-29 with a countdown). Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter and the vendor-adapter run flag the stale override.
Claude (Anthropic) claude-haiku-5-5 TBD (vendor has not confirmed a date) vendor source ↗ Anthropic lists claude-haiku-5-5 as Active, Deprecated N/A, Tentative retirement date "Not sooner than October 7, 2027" (page read 2026-10-09). That is the earliest day Anthropic allows itself to retire the model, not a retirement: retirement requires a Deprecated date and at least 60 days notice per the same page. Upstream added the model on 2026-10-08 with the floor (2027-10-07) as eol; serving it as end of life would say the model stops on a day Anthropic has not announced. Replace with the real retirement date the day Anthropic adds a Deprecated date; the claude adapter, sentinel claude-haiku-55-floor and the vendor-adapter run flag the stale override.
RouterOS 6.49 — vendor source ↗ MikroTik changelog: "What's new in 6.49.23 (2026-10-07)" (system stability, includes CVE-2026-84411); NEWEST6.long-term and NEWEST6.stable both read 6.49.23 with stamp 1791389116 = 2026-10-07T16:05Z. Upstream still served 6.49.22 / 2026-09-21. Read 2026-10-14 MT. Previous value 6.49.22 / 2026-09-16 (read 2026-09-25).
RouterOS 7.21 true vendor source ↗ MikroTik prints a policy, not end days. The Upgrading and installation page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical): 'Long term: Released rarely, and includes only the most critical fixes, upgrades within one number branch do not contain new features. When a Stable release has been out for a while and seems to be stable enough, it gets promoted into the long-term branch, replacing an older release, which is then moved to the archive.' Upstream serves eol 2026-05-26, the day 7.23 was first released (as stable), a day MikroTik never printed as the end of 7.21; the changelog itself shows 7.21.5 published in the Long-term channel on 2026-07-06, after that day. The Long-term channel now carries 7.23 (7.23.4 on 2026-09-03 through 7.23.8 on 2026-10-09) and lists no 7.21 build after 7.21.5, so 7.21 has been replaced and moved to the archive: ended, day not published, eol true. Pinned by sentinel routeros-long-term-replacement-policy. Retire when MikroTik prints an end day for 7.21.
RouterOS 7.20 true vendor source ↗ MikroTik prints a policy, not end days. The Upgrading and installation page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical): 'When a Stable release has been out for a while and seems to be stable enough, it gets promoted into the long-term branch, replacing an older release, which is then moved to the archive.' Upstream serves eol 2026-01-12, the day 7.21 was first released (as stable), a day MikroTik never printed as the end of 7.20; the changelog itself shows 7.20.8 published in the Long-term channel on 2026-02-02, after that day. The Long-term channel has since carried 7.21 (7.21.4 on 2026-04-21, 7.21.5 on 2026-07-06) and now 7.23, with no 7.20 build after 7.20.8: replaced and moved to the archive, ended, day not published, eol true. Pinned by sentinel routeros-long-term-replacement-policy. Retire when MikroTik prints an end day for 7.20.
Spring Boot 4.1 — vendor source ↗ Day the 4.1.0 release was published: GitHub release v4.1.0 and the Maven Central spring-boot 4.1.0 artifact agree (read 2026-09-25). Upstream served the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. The spring-boot adapter now compares releaseDate against the GitHub release day.
Spring Boot 4.0 — vendor source ↗ Day the 4.0.0 release was published: GitHub release v4.0.0 and the Maven Central spring-boot 4.0.0 artifact agree (read 2026-09-25). Upstream served the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. The spring-boot adapter now compares releaseDate against the GitHub release day.
Spring Boot 3.5 — vendor source ↗ Day the 3.5.0 release was published: GitHub release v3.5.0 and the Maven Central spring-boot 3.5.0 artifact agree (read 2026-09-25). Upstream served the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. The spring-boot adapter now compares releaseDate against the GitHub release day.
Spring Boot 3.4 — vendor source ↗ Day the 3.4.0 release was published: GitHub release v3.4.0 and the Maven Central spring-boot 3.4.0 artifact agree (read 2026-09-25). Upstream served the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. The spring-boot adapter now compares releaseDate against the GitHub release day.
Spring Boot 3.3 — vendor source ↗ Day the 3.3.0 release was published: GitHub release v3.3.0 and the Maven Central spring-boot 3.3.0 artifact agree (read 2026-09-25). Upstream served the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. The spring-boot adapter now compares releaseDate against the GitHub release day.
Spring Boot 3.2 — vendor source ↗ Day the 3.2.0 release was published: GitHub release v3.2.0 and the Maven Central spring-boot 3.2.0 artifact agree (read 2026-09-25). Upstream served the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. The spring-boot adapter now compares releaseDate against the GitHub release day.
Spring Boot 3.1 — vendor source ↗ Day the 3.1.0 release was published: GitHub release v3.1.0 and the Maven Central spring-boot 3.1.0 artifact agree (read 2026-09-25). Upstream served the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. The spring-boot adapter now compares releaseDate against the GitHub release day.
Spring Boot 2.7 — vendor source ↗ Day the 2.7.0 release was published: GitHub release v2.7.0 and the Maven Central spring-boot 2.7.0 artifact agree (read 2026-09-25). Upstream served the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. The spring-boot adapter now compares releaseDate against the GitHub release day.
Spring Boot 2.6 — vendor source ↗ Day the 2.6.0 release was published: GitHub release v2.6.0 and the Maven Central spring-boot 2.6.0 artifact agree (read 2026-09-25). Upstream served the month-end policy date from api.spring.io generations (initialReleaseDate is always the last day of the month), which printed as an exact release day on our pages. The spring-boot adapter now compares releaseDate against the GitHub release day.
Red Hat JBoss EAP 5 — vendor source ↗ Upstream extendedSupport is the ELS 1 end (2019-11-30). Red Hat lists a later Extended life cycle support (ELS) 2 phase for EAP 5.x ending 2022-11-30 (API read 2026-09-27). The site serves the latest ELS end, the last day Red Hat will support the line under any paid extension (Scott, 2026-09-27). tools/vendor-adapters/redhat-jboss-eap.mjs reads the same phase.
Red Hat JBoss EAP 6 — vendor source ↗ Upstream extendedSupport is the ELS 1 end (2022-06-30). Red Hat lists a later Extended life cycle support (ELS) 2 phase for EAP 6.x ending 2028-12-30 (API read 2026-09-27). The site serves the latest ELS end, the last day Red Hat will support the line under any paid extension (Scott, 2026-09-27). tools/vendor-adapters/redhat-jboss-eap.mjs reads the same phase.
Red Hat JBoss EAP 7 — vendor source ↗ Upstream extendedSupport is the ELS 1 end (2030-12-31). Red Hat lists a later Extended life cycle support (ELS) 2 phase for EAP 7.x ending 2031-12-31 (API read 2026-09-27). The site serves the latest ELS end, the last day Red Hat will support the line under any paid extension (Scott, 2026-09-27). tools/vendor-adapters/redhat-jboss-eap.mjs reads the same phase.
Red Hat JBoss EAP 8 — vendor source ↗ Upstream extendedSupport is the ELS 1 end (2033-02-05). Red Hat lists a later Extended life cycle support (ELS) 2 phase for EAP 8.x ending 2034-02-05 (API read 2026-09-27). The site serves the latest ELS end, the last day Red Hat will support the line under any paid extension (Scott, 2026-09-27). tools/vendor-adapters/redhat-jboss-eap.mjs reads the same phase.
Red Hat JBoss EAP 4.3 — vendor source ↗ Upstream extendedSupport is the ELS 1 end (2016-11-30). Red Hat lists a later Extended life cycle support (ELS) 2 phase for EAP 4.3 ending 2019-11-30 (API read 2026-09-27). The site serves the latest ELS end (Scott, 2026-09-27); tools/vendor-adapters/redhat-jboss-eap.mjs reads the same phase.
Red Hat JBoss EAP 4.2 — vendor source ↗ Upstream extendedSupport is the ELS 1 end (2015-06-30). Red Hat lists a later Extended life cycle support (ELS) 2 phase for EAP 4.2 ending 2018-06-30 (API read 2026-09-27). The site serves the latest ELS end (Scott, 2026-09-27); tools/vendor-adapters/redhat-jboss-eap.mjs reads the same phase.
Moodle 5.3 — vendor source ↗ Upstream endoflife.date added moodle 5.3 by 2026-10-05 with the same releaseDate, support, eol, lts and latest values as the override of 2026-10-05, so those five fields were retired (citation scan 2026-10-05 16:35 reported them redundant). Upstream gives latestReleaseDate 2026-10-03; the Moodle 5.3 release notes page is titled Moodle 5.3 (LTS) with release date 5 October 2026 and the releases table gives initial release 5 October 2026, so the vendor day is kept for the latest release.
Windows Server 2003 — vendor source ↗ Label only (2026-10-09): cycle 2003 is the original release, which Microsoft lists separately from SP1 and SP2; Windows Server 2003 itself was supported on SP2 to 2015-07-14. Guard checkSplitLineLabels.
Windows Server 2016 — vendor source ↗ Microsoft's lifecycle page for Windows Server 2016 (read 2026-10-06) prints start 10/15/2016, mainstream end 1/12/2022 and extended end 1/13/2027 PT and no Extended Security Updates end date; the February 25, 2026 announcement says ESU is available for up to three years and names no final day. Upstream endoflife.date serves extendedSupport 2030-01-12, a cadence estimate. Vendor floor rule: an estimated day is not served as a date. Retire this override when Microsoft prints an ESU end date (sentinel windows-server-2016-lifecycle-page).
OpenBSD 7.8 TBD (vendor has not confirmed a date) vendor source ↗ openbsd.org read 2026-10-06: 'The current release is OpenBSD 7.9, released May 19, 2026' and the FAQ says 'Only the two most recent OpenBSD releases receive security and reliability fixes for the base system.' OpenBSD publishes no end date for a release; a release leaves support on the day the second release after it ships. Upstream endoflife.date serves 2026-11-01 (the expected OpenBSD 8.0 day), the cadence estimate for a release that has not shipped. Vendor floor rule: an estimated day is not served as a date. Retire this entry when the next release ships (sentinel openbsd-current-release trips on the index page; set the eol to that release day).
OpenBSD 7.9 TBD (vendor has not confirmed a date) vendor source ↗ openbsd.org read 2026-10-06: 'The current release is OpenBSD 7.9, released May 19, 2026' and the FAQ says 'Only the two most recent OpenBSD releases receive security and reliability fixes for the base system.' OpenBSD publishes no end date for a release; a release leaves support on the day the second release after it ships. Upstream endoflife.date serves 2027-06-01 (the expected OpenBSD 8.1 day), the cadence estimate for a release that has not shipped. Vendor floor rule: an estimated day is not served as a date. Retire this entry when the next release ships (sentinel openbsd-current-release trips on the index page; set the eol to that release day).
MariaDB 13.0 TBD (vendor has not confirmed a date) vendor source ↗ mariadb.org maintenance policy read 2026-10-06: the rolling releases table prints 13.0 with Community EOL 'Q4 2026' (quarter precision) and 13.1 with release date 'Sep 2026' and Community EOL 'Q1 2027'; a rolling release is maintained until the next one ships and MariaDB names no day. Upstream endoflife.date serves 2026-12-31, the quarter end. Vendor floor rule: an estimated day is not served as a date. Retire when MariaDB prints the day (sentinel mariadb-rolling-13-0 trips when the row changes) or when 13.1 ships and 13.0's end is a real date.
Veeam Backup for Microsoft 365 7 2025-06-30 vendor source ↗ Veeam product lifecycle page read 2026-10-06: Veeam Backup for Microsoft 365 7 | Released February 2023 | End of Fix December 2023 | End of Support and Security Fix June 2025; last month of service rule gives 2025-06-30. Upstream serves 2026-06-28. Sentinel veeam-lifecycle-vb365. | Veeam product lifecycle page read twice 2026-10-09; page rule: "The specified month is the last month when the relevant service is offered." VB365 7 End of Fix December 2023 = 2023-12-31 (upstream 2023-12-28).
Veeam Backup for Microsoft 365 8 2027-05-31 vendor source ↗ Veeam product lifecycle page (veeam.com/product-lifecycle.html) read 2026-10-06: Veeam Backup for Microsoft 365 8 | Released September 2024 | End of Fix Next GA Date | End of Support and Security Fix May 2027, with the page rule 'The specified month is the last month when the relevant service is offered', so the last day of service is 2027-05-31. Upstream endoflife.date serves 2026-09-03 (release date plus two years), which is wrong: Veeam shipped 8.6.0.1102 on 2026-09-14. Sentinel veeam-lifecycle-vb365.
Mattermost 10.11 — vendor source ↗ Mattermost server releases page read 2026-10-07 labels 10.11 EXTENDED (Extended Support Release: maintained for a longer period, backports for security fixes and major bug fixes, released every 9 months, supported for 12 months, per docs.mattermost.com/product-overview/release-policy.html); upstream endoflife.date carries lts false for it. Served lts true so the LTS guard matches the vendor's own label.
Mattermost 11.7 — vendor source ↗ Mattermost server releases page read 2026-10-07 labels 11.7 EXTENDED (Extended Support Release: maintained for a longer period, backports for security fixes and major bug fixes, released every 9 months, supported for 12 months, per docs.mattermost.com/product-overview/release-policy.html); upstream endoflife.date carries lts false for it. Served lts true so the LTS guard matches the vendor's own label.
Ansible Core 2.21 — vendor source ↗ Upstream serves the month-end 2026-05-31 for the 2.21 GA (the support matrix prints GA: May 2026). The 2.21 roadmap names 2026-05-18 Release and PyPI shows ansible-core 2.21.0 uploaded 2026-05-18T20:52Z. Month-end policy dates trap: release days come from the release artifact.
Veeam Backup & Replication 11 2024-02-29 vendor source ↗ Veeam product lifecycle page read twice 2026-10-09; page rule: "The specified month is the last month when the relevant service is offered." 11 End of Fix February 2023, End of Support February 2024 (upstream served the first of each month).
Veeam Backup & Replication 12 — vendor source ↗ Veeam product lifecycle page (veeam.com/product-lifecycle.html) read 2026-10-09: Veeam Backup & Replication 12 | Released February 2023 | End of Fix November 2025 | End of Support and Security Fix February 2027, with the page rule that the specified month is the last month when the relevant service is offered; Veeam KB4934 (12.3.2 P4, read the same day) states that version 12 will reach End of Support on 2027-02-28. Upstream endoflife.date serves 2027-02-01, the first day of the month instead of the last, which would call 12 unsupported 27 days early. Same correction as veeam-backup-for-microsoft-365 on 2026-10-06. Sentinels veeam-lifecycle-vbr and veeam-kb4934-vbr12-eos. The support field (upstream 2025-09-03, the 13 release day) is left alone: Veeam prints End of Fix November 2025, so the vendor day would be 2025-11-30; both are past. | Veeam product lifecycle page read twice 2026-10-09; page rule: "The specified month is the last month when the relevant service is offered." 12 End of Fix November 2025 = 2025-11-30 (upstream 2025-09-03, the 13 release day). Found by tools/month-precision-scan.mjs.
Alpine Linux 3.23 — vendor source ↗ Alpine's releases table (alpinelinux.org/releases) prints the v3.23 branch date 2025-12-03 and the release announcement 'Alpine 3.23.0 released' is dated 2025-12-03 (also listed under that day in the news archive), both read 2026-10-09. Upstream endoflife.date serves 2025-12-04. The 2026-09-28 verification note called this branch date versus announcement date; it is not, the announcement is dated 2025-12-03 too.
Veeam ONE 11 2024-02-29 vendor source ↗ Veeam product lifecycle page read twice 2026-10-09; page rule: "The specified month is the last month when the relevant service is offered." Veeam ONE 11 End of Fix February 2023, End of Support February 2024 (upstream served the first of each month).
Veeam ONE 12 2027-02-28 vendor source ↗ Veeam product lifecycle page read twice 2026-10-09; page rule: "The specified month is the last month when the relevant service is offered." Veeam ONE 12 End of Fix September 2025, End of Support February 2027 (upstream 2025-09-03 and 2027-02-01).
Veeam ONE 13 2028-11-30 vendor source ↗ Veeam product lifecycle page read twice 2026-10-09; page rule: "The specified month is the last month when the relevant service is offered." Veeam ONE 13 End of Fix and End of Support November 2028 (upstream served support true and eol false).
Kiali 2.25 2026-10-12 vendor source ↗ Kiali publishes no end-of-life dates. Its prerequisites page, read 2026-10-09, states 'Supported Kiali versions include only the Kiali versions associated with supported Istio versions.' and its compatibility table lists Istio 1.30 with Kiali '2.26 and higher', 1.29 with '2.21 and higher', 1.28 with '2.17-2.30' (out of support) and 1.27 with '2.12-2.25' (out of support). The newest Istio Kiali 2.21 to 2.25 are tested with is therefore 1.29, and they leave support when it does. Istio's supported releases page, read 2026-10-09, prints 1.29 End of Life '12 Oct 2026 (Expected)' (served via the istio 1.29 override). Upstream endoflife.date uses the same derivation but with its own Istio 1.29 date (2026-10-31), which the istio override already corrects. Istio marks the date Expected: if the istio vendor adapter moves the istio 1.29 eol, move kiali 2.21 to 2.25 with it (golden cases kiali-225-eol-with-istio-129 and kiali-221-eol-with-istio-129 and two prose claims in article-kiali-eol bind the Kiali side; sentinel kiali-istio-support-rule pins the rule and table).
Kiali 2.24 2026-10-12 vendor source ↗ Same as kiali 2.25: Kiali's rule 'Supported Kiali versions include only the Kiali versions associated with supported Istio versions.' plus its table (1.29 row '2.21 and higher', 1.30 row '2.26 and higher') make Istio 1.29 the newest Istio 2.24 is tested with; Istio prints 1.29 End of Life '12 Oct 2026 (Expected)'. Both pages read 2026-10-09. Upstream 2026-10-31 is its own Istio 1.29 date. Move with the istio 1.29 eol.
Kiali 2.23 2026-10-12 vendor source ↗ Same as kiali 2.25: Kiali's rule 'Supported Kiali versions include only the Kiali versions associated with supported Istio versions.' plus its table (1.29 row '2.21 and higher', 1.30 row '2.26 and higher') make Istio 1.29 the newest Istio 2.23 is tested with; Istio prints 1.29 End of Life '12 Oct 2026 (Expected)'. Both pages read 2026-10-09. Upstream 2026-10-31 is its own Istio 1.29 date. Move with the istio 1.29 eol.
Kiali 2.22 2026-10-12 vendor source ↗ Same as kiali 2.25: Kiali's rule 'Supported Kiali versions include only the Kiali versions associated with supported Istio versions.' plus its table (1.29 row '2.21 and higher', 1.30 row '2.26 and higher') make Istio 1.29 the newest Istio 2.22 is tested with; Istio prints 1.29 End of Life '12 Oct 2026 (Expected)'. Both pages read 2026-10-09. Upstream 2026-10-31 is its own Istio 1.29 date. Move with the istio 1.29 eol. (Upstream marks 2.22 as the Kiali in OpenShift Service Mesh 3.3; Red Hat's own lifecycle for that product is separate and not changed here.)
Kiali 2.21 2026-10-12 vendor source ↗ Same as kiali 2.25: Kiali's rule 'Supported Kiali versions include only the Kiali versions associated with supported Istio versions.' plus its table (1.29 row '2.21 and higher', 1.30 row '2.26 and higher') make Istio 1.29 the newest Istio 2.21 is tested with; Istio prints 1.29 End of Life '12 Oct 2026 (Expected)'. Both pages read 2026-10-09. Upstream 2026-10-31 is its own Istio 1.29 date. Move with the istio 1.29 eol.
Kiali 2.32 2026-12-31 vendor source ↗ Kiali v2.32.0 published 2026-09-13T14:25:27Z (GitHub releases API and the release page, read twice 2026-10-09; no 2.32.x patch). Kiali prints no dates of its own; its prerequisites page (read 2026-10-09) says 'Supported Kiali versions include only the Kiali versions associated with supported Istio versions.' and its table lists Istio 1.30 with '2.26 and higher' and 1.29 with '2.21 and higher' (no 1.31 row yet), so 2.32 is tested with 1.29 and 1.30 and leaves support with Istio 1.30. Istio's supported releases page prints 1.30 End of Life '~Dec 2026 (Expected)'; we serve istio 1.30 and kiali 2.26 to 2.31 as 2026-12-31 (upstream), and this follows them. If the director applies the vendor floor rule to istio 1.30 (eol false until Istio names a day), this eol moves to false with it; if Kiali adds an Istio 1.31 row covering 2.32, it moves to the istio 1.31 eol. Upstream endoflife.date tops out at 2.31. Retire when upstream adds 2.32.
Kiali 2.33 2026-12-31 vendor source ↗ Kiali v2.33.0 published 2026-10-04T14:37:06Z (GitHub releases API and the release page, read twice 2026-10-09). Same derivation as kiali 2.32: Kiali's rule 'Supported Kiali versions include only the Kiali versions associated with supported Istio versions.' with table rows Istio 1.30 '2.26 and higher' and 1.29 '2.21 and higher' (no 1.31 row), so 2.33 leaves support with Istio 1.30, printed '~Dec 2026 (Expected)' and served 2026-12-31 for istio 1.30 and kiali 2.26 to 2.31. Moves with istio 1.30 (or to istio 1.31 if Kiali adds that row). Retire when upstream adds 2.33.
Microsoft SQL Server 13.0 — vendor source ↗ Label only, no date change (2026-10-09, grounding-queries audit): cycle 2016 RTM is the original release (RTM) line, which Microsoft lists separately from its service packs; its end date is the RTM date, not the product date. Labelled the whole product, the version page title read as if SQL Server 2016 itself had ended then. Guard checkSplitLineLabels.
Microsoft SQL Server 12.0 — vendor source ↗ Label only, no date change (2026-10-09, grounding-queries audit): cycle 2014 RTM is the original release (RTM) line, which Microsoft lists separately from its service packs; its end date is the RTM date, not the product date. Labelled the whole product, the version page title read as if SQL Server 2014 itself had ended then. Guard checkSplitLineLabels.
Microsoft SQL Server 11.0 — vendor source ↗ Label only, no date change (2026-10-09, grounding-queries audit): cycle 2012 RTM is the original release (RTM) line, which Microsoft lists separately from its service packs; its end date is the RTM date, not the product date. Labelled the whole product, the version page title read as if SQL Server 2012 itself had ended then. Guard checkSplitLineLabels.
Microsoft SQL Server 10.00 — vendor source ↗ Label only, no date change (2026-10-09, grounding-queries audit): cycle 2008 RTM is the original release (RTM) line, which Microsoft lists separately from its service packs; its end date is the RTM date, not the product date. Labelled the whole product, the version page title read as if SQL Server 2008 itself had ended then. Guard checkSplitLineLabels.
Microsoft SQL Server 9.0 — vendor source ↗ Label only, no date change (2026-10-09, grounding-queries audit): cycle 2005 RTM is the original release (RTM) line, which Microsoft lists separately from its service packs; its end date is the RTM date, not the product date. Labelled the whole product, the version page title read as if SQL Server 2005 itself had ended then. Guard checkSplitLineLabels.
Python 3.15 — vendor source ↗ Upstream added 3.15 on 2026-10-10 (endoflife.date PR 11311) with support 2028-10-09, a day Python never printed: the devguide prints the bugfix end only as a month (2028-10) and PEP 790 names no day. Vendor floor rule: support true until Python prints a day. The other fields agreed with upstream and were retired 2026-10-11.
Splunk 10.6 2028-09-30 vendor source ↗ Splunk Software Support Policy, Splunk Enterprise table (columns Version, Release Date, End of Splunk Enterprise Support Date, criteria, End of Splunk Cloud Platform Support Date, criteria), row '10.6 Sep 30 2026 Sep 30 2028 24 Months Sep 30 2027 12 Months', read twice 2026-10-09. Released for Splunk Enterprise on-premises (unlike 10.3 and 10.5, which print 'Not Released' for Enterprise and which upstream rightly omits); the Splunk Enterprise download page offers 10.6.0.5 (read 2026-10-09). eol is the Enterprise end of support date, the field upstream uses for 10.4 (2028-05-18). Upstream endoflife.date tops out at 10.4 and no upstream PR was found. Retire when upstream adds 10.6.
Apache Tomcat 9.0 TBD (vendor has not confirmed a date) vendor source ↗ Apache Tomcat whichversion.html (curl with the build UA, read twice 2026-10-09): "End of support for Tomcat 9.0.x is expected no earlier than 31 March 2027." and "Extended support will be provided via a new 9.1.x branch that will be started when 9.0.x reaches end of support." That is a floor, not an end date: Apache has not named the day 9.0.x support ends. Upstream endoflife.date serves 2027-03-31 as eol, which would show 9.0 as ending on that day with a countdown. Vendor floor rule: eol false until Apache names the day. Articles state the floor in words, guarded by sentinel tomcat-90-eos-floor. Retire when Apache publishes a 9.0.x end of support date (the sentinel trips when the sentence changes).
MongoDB 9.0 — vendor source ↗ 2026-10-11 (audit Q7): MongoDB 9.0 release notes heading '9.0.0 - Sept 28, 2026' (9.0.1 and 9.0.2 also Sept 28, 2026). Upstream serves releaseDate 2026-09-30. Read twice 2026-10-11 (curl with a browser UA and the built-in browser).
Ember.js 6.8 — vendor source ↗ 2026-10-11 (audit Q6): the npm registry time for ember-source 6.8.0 is 2025-10-13T19:47:24.973Z (UTC day 2025-10-13); upstream serves 2025-10-25, a later blog or announcement day. The vX.Y.0 publish to npm is the release. Read twice 2026-10-11 (curl of the registry document and the same document in the built-in browser).
Ember.js 6.9 — vendor source ↗ 2026-10-11 (audit Q6): the npm registry time for ember-source 6.9.0 is 2025-11-25T20:09:56.939Z (UTC day 2025-11-25); upstream serves 2026-01-09, a later blog or announcement day. The vX.Y.0 publish to npm is the release. Read twice 2026-10-11 (curl of the registry document and the same document in the built-in browser).
Ember.js 6.10 — vendor source ↗ 2026-10-11 (audit Q6): the npm registry time for ember-source 6.10.0 is 2026-01-06T18:37:34.726Z (UTC day 2026-01-06); upstream serves 2026-02-06, a later blog or announcement day. The vX.Y.0 publish to npm is the release. Read twice 2026-10-11 (curl of the registry document and the same document in the built-in browser).
Ember.js 6.11 — vendor source ↗ 2026-10-11 (audit Q6): the npm registry time for ember-source 6.11.0 is 2026-02-17T19:17:36.602Z (UTC day 2026-02-17); upstream serves 2026-03-06, a later blog or announcement day. The vX.Y.0 publish to npm is the release. Read twice 2026-10-11 (curl of the registry document and the same document in the built-in browser).
Ember.js 6.12 — vendor source ↗ 2026-10-11 (audit Q6): the npm registry time for ember-source 6.12.0 is 2026-03-31T22:18:12.452Z (UTC day 2026-03-31); upstream serves 2026-05-01, a later blog or announcement day. The vX.Y.0 publish to npm is the release. Read twice 2026-10-11 (curl of the registry document and the same document in the built-in browser).
Ember.js 7.0 — vendor source ↗ 2026-10-11 (audit Q6): the npm registry time for ember-source 7.0.0 is 2026-05-12T03:06:57.388Z (UTC day 2026-05-12); upstream serves 2026-05-29, a later blog or announcement day. The vX.Y.0 publish to npm is the release. Read twice 2026-10-11 (curl of the registry document and the same document in the built-in browser).
Ember.js 7.1 — vendor source ↗ 2026-10-11 (audit Q6): the npm registry time for ember-source 7.1.0 is 2026-06-22T20:59:00.730Z (UTC day 2026-06-22); upstream serves 2026-07-26, a later blog or announcement day. The vX.Y.0 publish to npm is the release. Read twice 2026-10-11 (curl of the registry document and the same document in the built-in browser).
Ember.js 7.2 — vendor source ↗ 2026-10-11 (audit Q6): the npm registry time for ember-source 7.2.0 is 2026-08-09T19:50:33.386Z (UTC day 2026-08-09); upstream serves 2026-09-08, a later blog or announcement day. The vX.Y.0 publish to npm is the release. Read twice 2026-10-11 (curl of the registry document and the same document in the built-in browser).
Ember.js 7.3 — vendor source ↗ 2026-10-11 (audit Q6): the npm registry time for ember-source 7.3.0 is 2026-09-14T21:21:29.288Z (UTC day 2026-09-14); upstream serves 2026-10-05, a later blog or announcement day. The vX.Y.0 publish to npm is the release. Read twice 2026-10-11 (curl of the registry document and the same document in the built-in browser).
Jira Software 9.14 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 9.14 print "Issues resolved in 9.14.0 Released on 13 Feb 2024"; upstream serves 2024-02-14. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day LATE here, the opposite of the usual Atlassian pattern. The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Jira Software 8.19 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 8.19 print "Issues resolved in 8.19.0 Released on 26 August 2021"; upstream serves 2021-08-25. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Bitbucket 10.0 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 10.0 print "Resolved issues in Bitbucket Data Center 10.0 Released 08 September 2025"; upstream serves 2025-09-07. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Bitbucket 9.4 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 9.4 print "Resolved issues in Bitbucket Data Center 9.4.0 Released 3 December 2024"; upstream serves 2024-12-02. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Bitbucket 8.15 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 8.15 print "Resolved issues in Bitbucket Data Center 8.15.0 Released 24 October 2023"; upstream serves 2023-10-23. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Bitbucket 9.6 — vendor source ↗ vendor adapter bitbucket: vendor publishes releaseDate "2025-03-18", upstream "2025-03-17" (read twice, 2026-10-12)
Bamboo 11.0 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 11.0 print "Bamboo 11.0.0 Release date: 30 Apr 2025; Issues resolved in Bamboo 11.0.0 Released on 30 Apr 2025"; upstream serves 2025-04-29. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Bamboo 10.2 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 10.2 print "Issues resolved in Bamboo 10.2.0 Released on 20 Dec 2024"; upstream serves 2024-12-19. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Bamboo 9.1 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 9.1 print "Issues resolved in Bamboo 9.1.0 Released on 15 Dec 2022"; upstream serves 2022-12-14. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Bamboo 12.1 — vendor source ↗ vendor adapter bamboo: vendor publishes releaseDate "2025-12-17", upstream "2025-12-16" (read twice, 2026-10-12)
Bamboo 10.1 — vendor source ↗ vendor adapter bamboo: vendor publishes releaseDate "2024-11-20", upstream "2024-11-19" (read twice, 2026-10-12)
Jira Service Management 5.14 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 5.14 print "Issues resolved in 5.14.0 Released on 13 February 2024"; upstream serves 2024-02-14. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day LATE here, the opposite of the usual Atlassian pattern. The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Jira Service Management 4.19 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 4.19 print "Issues resolved in 4.19.0 Released on 26 August 2021"; upstream serves 2021-08-25. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
Jira Service Management 4.17 — vendor source ↗ 2026-10-11 (audit Q3): Atlassian release notes for 4.17 print "Issues resolved in 4.17.0 Released on 18 May 2021"; upstream serves 2021-05-17. Read twice 2026-10-11 (curl with a browser UA and the built-in browser). Upstream is a day early here, the pattern seen on about 136 Atlassian cycles (eol = upstream release + 2 years + 1 day). The confluence, jira-software, bitbucket and bamboo adapters now read this day.
SapMachine 11 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 11 (LTS) | 09/2018 | 12/2024' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2024-12-01 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 12 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 12 | 03/2019 | 09/2019' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2019-09-18 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 13 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 13 | 09/2019 | 03/2020' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2020-03-18 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 14 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 14 | 03/2020 | 09/2020' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2020-09-16 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 15 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 15 | 09/2020 | 03/2021' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2021-03-15 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 16 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 16 | 03/2021 | 09/2021' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2021-09-14 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 17 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 17 (LTS) | 09/2021 | 09/2026' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2026-09-01 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 18 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 18 | 03/2022 | 09/2022' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2022-09-19 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 19 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 19 | 09/2022 | 03/2023' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2023-03-17 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 20 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 20 | 03/2023 | 09/2023' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2023-09-19 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 21 TBD (vendor has not confirmed a date) vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the row 'SapMachine 21 (LTS) | 09/2023 | 09/2028' (Release | General Availability | End of Life) and no day for any release. Upstream's 2028-09-01 is the first of that month, an invented day: endoflife.date's sapmachine.md computes eol from release dates and SAP names no day. The only policy sentence is 'SapMachine supports LTS releases for at least four years.' eol stays false until SAP prints a day (vendor floor dates rule); the vendor row is pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 22 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 22 | 03/2024 | 09/2024' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2024-09-17 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 23 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 23 | 09/2024 | 03/2025' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2025-03-18 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 24 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 24 | 03/2025 | 09/2025' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2025-09-16 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 25 TBD (vendor has not confirmed a date) vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the row 'SapMachine 25 (LTS) | 09/2025 | 09/2030' and no day for any release. Upstream's 2030-09-30 is the last day of that month, an invented day (upstream used the first of the month for 21 and the last for 25, which shows neither came from SAP). Policy sentence: 'SapMachine supports LTS releases for at least four years.' eol stays false until SAP prints a day (vendor floor dates rule); pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 26 true vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 26 | 03/2026 | 09/2026' (Release | General Availability | End of Life) under 'Unsupported Releases' and no day for any release. Upstream's 2026-09-15 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month has passed and SAP lists the release as out of support, so eol is true: ended, day not published. Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
SapMachine 27 TBD (vendor has not confirmed a date) vendor source ↗ SAP's SapMachine Maintenance and Support page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the cell 'SapMachine 27 | 09/2026 | 03/2027' (Release | General Availability | End of Life) under 'Supported Releases' and no day for any release. Upstream's 2027-03-31 is a day inside that month that SAP never printed (endoflife.date's sapmachine.md computes non-LTS eol as releaseDate(x+1)). The month is still ahead, so eol stays false until SAP prints a day (vendor floor dates rule). Row pinned by sentinel sapmachine-lts-eol-months. Retire when upstream carries an SAP-named day.
Cortex XDR 7.9.103-ce 2027-12-31 vendor source ↗ Palo Alto Networks End-of-Life Summary, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the row '7.9.103 CE (Cortex XDR agent) | November 11, 2024 | December 31, 2027**' with footnote '** 7.9.103 CE is supported only for Win 7 and Server 2008R2.' Upstream (endoflife.date pan-cortex-xdr) serves eol 2026-12-31, one year early. Every other served cortex-xdr cycle's releaseDate and eol matched the vendor table on the same read. Pinned by sentinel cortex-xdr-7-9-103-ce-eol. Retire when upstream serves 2027-12-31.
Apache ActiveMQ 6.2 2026-09-05 vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves eol false for 6.2 (endoflife.date apache-activemq.md: 'still listed on current_releases.yml', the download-stream list). The rendered page says otherwise: 6.2.x is 'Inactive' in both tables. The day is the vendor's own status change: the page source src/components/classic/download/index.md in apache/activemq-website read 6.2.x as '**Stable - Supported**' at commit 6a25a976 (2026-08-10) and as '_Inactive_' from commit 8034649c (2026-09-05 18:22 UTC, Matt Pavlovich), the same method endoflife.date used for the 6.1 day (commit 35990cf8, 2025-12-02) and the 6.0, 5.18 and 5.17 days. 6.2.10 (Sep 26th, 2026) shipped after the change and the status stayed Inactive (commit 5c537b68). Pinned by sentinel apache-activemq-inactive-status. Retire when upstream serves a day for 6.2.
Apache ActiveMQ 5.16 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2023-03-18 for 5.16. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.15 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2022-03-09 for 5.15. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.14 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2017-06-27 for 5.14. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.13 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2016-12-16 for 5.13. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.12 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2016-02-03 for 5.12. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.11 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2016-02-03 for 5.11. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.10 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2015-02-13 for 5.10. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.9 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2014-06-05 for 5.9. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.8 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2013-10-14 for 5.8. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.7 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2013-02-06 for 5.7. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.6 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2012-10-02 for 5.6. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.5 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2012-05-02 for 5.5. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.4 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2011-10-12 for 5.4. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.3 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2010-08-13 for 5.3. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.2 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2009-10-23 for 5.2. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.1 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2009-06-30 for 5.1. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache ActiveMQ 5.0 true vendor source ↗ Apache ActiveMQ Classic download page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints only 6.3.x and 5.19.x as Active and every other listed series as Inactive, with the status definition 'Inactive: Reached end-of-life and is no longer actively maintained. Inactive versions do not receive updates.' Apache prints no end day for any series. Upstream serves 2008-05-01 for 5.0. Upstream's day for this cycle is marked in endoflife.date's apache-activemq.md as 'estimated based on' a later release date and was never printed by Apache. The series is Inactive on the vendor page (Schedule & Status table, 5.10.x and newer) or older than every series the page lists (5.9.x and older are on the past releases page only); the vendor's Active list is exhaustive. Ended, day not published: eol true. Pinned by sentinel apache-activemq-inactive-status. Retire when upstream carries an Apache-named day.
Apache Solr 5 true vendor source ↗ Apache Solr downloads page, section About Versions and Support, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical): 'Apache Solr is under active development with frequent feature releases on the current major version. The previous major version will see occasional critical security- or bug fixes releases. Older versions are considered EOL (End Of Life) and will not be further updated.' Solr 10.0.0 is the current major and 9.11.0 the last release of the previous major, so Solr 5 is EOL under the policy, but Apache printed no end day for it: upstream's 2017-10-24 is the day of the news item '24 October 2017, Apache Solr 5.5.5 available' (the last 5.x release), not an EOL announcement (solr.md: eol(x) = releaseDate(x+2) or announcement on news.html). Ended, day not published: eol true. Solr 8's 2024-10-25 is confirmed by the news item '25 October 2024, Solr 8 reaches End-Of-Life' and is left alone. Pinned by sentinel solr-versions-and-support-policy. Retire when upstream carries an Apache-named day.
Quarkus 1 2021-06-30 vendor source ↗ Upstream aggregates every 1.x line as cycle 1 with eol 2021-06-23, the day the 2.0.0.Final git tag was created, not the day it shipped. The vendor eol table, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), prints the last 1.x line as '1.13 | 2021-03-30 | 2021-06-30 | 1.13.7.Final' (End of Life 2021-06-30) and the releases table prints 2.0 released 2021-06-30; the GitHub release 2.0.0.Final was published 2021-06-30T14:29Z. Policy on the releases page: 'Non-LTS releases are supported until the next minor release.' Serve the vendor's day. Pinned by sentinel quarkus-eol-table. Retire when upstream serves 2021-06-30.
Quarkus 3.39 — vendor source ↗ Quarkus end-of-life page and releases page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), both print 3.39 Released 2026-08-26 (eol table row '3.39 | 2026-08-26 | 2026-09-30 | 3.39.5'; releases table row '3.39 | 2026-08-26 | Ended 2026-09-30'). GitHub release 3.39.0 was published 2026-08-26T17:06Z. Upstream serves 2026-08-27, the date of the quarkus.io blog post 'Quarkus 3.39 released' (August 27, 2026), one day after the vendor's lifecycle tables. The lifecycle tables govern. Pinned by sentinel quarkus-eol-table. Retire when upstream serves 2026-08-26.
Quarkus 3.38 2026-08-26 vendor source ↗ Quarkus end-of-life page and releases page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), both print 3.38 End of Life 2026-08-26 (eol table row '3.38 | 2026-07-29 | 2026-08-26 | 3.38.3'; releases table 'Ended 2026-08-26'), the day 3.39.0 shipped under the stated policy 'Non-LTS releases are supported until the next minor release.' Upstream serves 2026-08-27 (the 3.39 blog-post day). Pinned by sentinel quarkus-eol-table. Retire when upstream serves 2026-08-26.
Quarkus 3.32 — vendor source ↗ Quarkus end-of-life page and releases page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical), both print 3.32 Released 2026-02-25 (eol table row '3.32 | 2026-02-25 | 2026-03-25 | 3.32.4'; releases table '3.32 | 2026-02-25 | Ended 2026-03-25'). GitHub release 3.32.0 was published 2026-02-25T15:20Z. Upstream serves 2026-02-26, the quarkus.io blog-post day (February 26, 2026). The vendor tables print 3.31 End of Life 2026-02-26, which upstream already serves and is left alone. Pinned by sentinel quarkus-eol-table. Retire when upstream serves 2026-02-25.
Nexus 3.53 — vendor source ↗ Sonatype Nexus Repository 3 Versions Status table and the 3.53 release notes, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical): the table prints Initial Release Date 'May 02, 2023 (3.53.0)' and the release notes print '3.53.0 Released May 2, 2023'. Upstream serves releaseDate 2023-05-03 and support 2024-05-03 (its own 12-month formula on the wrong day). The table's Extended Maintenance cell for this row reads 'May 02, 2023', a vendor typo that equals the release day; the page's own rule is 'Sonatype Nexus Repository releases are considered generally available and fully supported for a term of 1 year after the version's release date' and the row's Sunset Date 'November 02, 2024' is exactly six months after May 02, 2024, so support is served as 2024-05-02. The sunset day 2024-11-02 matches upstream and is left alone. The other 67 cycles on the table (3.96 down to 3.29) match upstream to the day on releaseDate, support and eol. Pinned by sentinel sonatype-nexus-3-versions-status. Retire when upstream serves 2023-05-02 / 2024-05-02.
Keycloak 14.0 2021-07-30 vendor source ↗ Keycloak security policy, read 2026-10-11 two ways (raw SECURITY.md with curl and the GitHub policy page in the built-in browser, identical): 'Depending on the severity of a vulnerability, the issue may be fixed in the current major.minor release of Keycloak, or for lower severity vulnerabilities or hardening in the following major.minor release.' Keycloak prints no end days; a minor line ends when the next ships, which is upstream's own rule (eol(x) = release(x+1)) and holds for every other row checked (26.8 down to 15.0 against GitHub release dates, all exact). The 14.0 row alone deviates: upstream serves 2021-07-15 while 15.0.0 was released 2021-07-30 (GitHub release published 2021-07-30T12:02Z, read twice). Pinned by sentinel keycloak-security-policy-current-release. Retire when upstream serves 2021-07-30.
SonarQube Server 2026.5 TBD (vendor has not confirmed a date) vendor source ↗ Sonar prints a policy, not a day. Release cycle model page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical): 'This policy applies to LTA releases starting with 2026.5. Developer Edition, Enterprise Edition, and Data Center Edition customers get 12 months of patches from the release date. Enterprise Edition and Data Center Edition customers with Enterprise Support get 18 months of patches.' and 'Which versions of SonarQube Server are patched? The latest version of SonarQube Server. Each LTA, for as long as it receives patches under the patch policy above'. Upstream serves 2028-03-01, a day Sonar prints nowhere (docs, LTA page, downloads, historical downloads) and that matches neither 12 nor 18 months from the 2026-09-29 release. Vendor floor rule: the LTA has not ended and no day is named, eol false. Pinned by sentinel sonarqube-server-lta-patch-policy. Retire when Sonar prints an end day for 2026.5.
SonarQube Server 2026.1 TBD (vendor has not confirmed a date) vendor source ↗ Sonar prints a policy, not a day. Release cycle model page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical): 'Which versions of SonarQube Server are patched? The latest version of SonarQube Server. Each LTA, for as long as it receives patches under the patch policy above'; the dated patch policy (12 or 18 months) 'applies to LTA releases starting with 2026.5'. Upstream serves 2027-08-02, a day Sonar prints nowhere and that no stated rule produces from the 2026-01-30 release. 2026.1 LTA is still listed as Previous Long Term Active on Sonar's historical downloads page. Vendor floor rule: not ended, no day named, eol false. Pinned by sentinel sonarqube-server-lta-patch-policy. Retire when Sonar prints an end day for 2026.1.
SonarQube Server 2025.4 TBD (vendor has not confirmed a date) vendor source ↗ Sonar prints a policy, not a day. Release cycle model page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical): 'Which versions of SonarQube Server are patched? The latest version of SonarQube Server. Each LTA, for as long as it receives patches under the patch policy above'; the dated patch policy (12 or 18 months) 'applies to LTA releases starting with 2026.5'. Upstream serves 2027-01-30, a day Sonar prints nowhere. 2025.4 LTA is still listed as Previous Long Term Active Version on Sonar's historical downloads page and received 2025.4.9 on 2026-09-23. Vendor floor rule: not ended, no day named, eol false. Pinned by sentinel sonarqube-server-lta-patch-policy. Retire when Sonar prints an end day for 2025.4.
SonarQube Server 2025.1 true vendor source ↗ Sonar prints a policy, not a day. Release cycle model page, read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical): 'Which versions of SonarQube Server are patched? The latest version of SonarQube Server. Each LTA, for as long as it receives patches under the patch policy above'; the dated patch policy 'applies to LTA releases starting with 2026.5'. Upstream serves 2026-07-01, a day Sonar prints nowhere; it is past, three newer LTAs (2025.4, 2026.1, 2026.5) have shipped and the last 2025.1 patch was 2025.1.8 on 2026-05-29. Ended, day not published: eol true. Pinned by sentinel sonarqube-server-lta-patch-policy. Retire when Sonar prints the end day for 2025.1.
HAProxy 3.4 TBD (vendor has not confirmed a date) vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2031-Q2 (LTS)' for branch 3.4. The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2031-04-01, the first day of that quarter, a day HAProxy never printed. Vendor floor rule: the branch has not ended and no day is named, eol false (the quarter is in the vendor sentence). Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 3.4.
HAProxy 3.3 TBD (vendor has not confirmed a date) vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2027-Q1 (stable)' for branch 3.3. The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2027-01-01, the first day of that quarter, a day HAProxy never printed. Vendor floor rule: the branch has not ended and no day is named, eol false (the quarter is in the vendor sentence). Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 3.3.
HAProxy 3.2 TBD (vendor has not confirmed a date) vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2030-Q2 (LTS)' for branch 3.2. The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2030-04-01, the first day of that quarter, a day HAProxy never printed. Vendor floor rule: the branch has not ended and no day is named, eol false (the quarter is in the vendor sentence). Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 3.2.
HAProxy 3.0 TBD (vendor has not confirmed a date) vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2029-Q2 (LTS)' for branch 3.0. The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2029-04-01, the first day of that quarter, a day HAProxy never printed. Vendor floor rule: the branch has not ended and no day is named, eol false (the quarter is in the vendor sentence). Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 3.0.
HAProxy 2.8 TBD (vendor has not confirmed a date) vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2028-Q2 (critical fixes only)' for branch 2.8. The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2028-04-01, the first day of that quarter, a day HAProxy never printed. Vendor floor rule: the branch has not ended and no day is named, eol false (the quarter is in the vendor sentence). Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 2.8.
HAProxy 2.6 TBD (vendor has not confirmed a date) vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2027-Q2 (critical fixes only)' for branch 2.6. The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2027-04-01, the first day of that quarter, a day HAProxy never printed. Vendor floor rule: the branch has not ended and no day is named, eol false (the quarter is in the vendor sentence). Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 2.6.
HAProxy 3.1 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2026-Q1 (unmaintained)' for branch 3.1 (latest 3.1.17 2026-03-19). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2026-01-01 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 3.1.
HAProxy 2.9 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2025-Q1 (unmaintained)' for branch 2.9 (latest 2.9.15 2025-03-21). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2025-03-21 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 2.9.
HAProxy 2.7 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2024-Q1 (unmaintained)' for branch 2.7 (latest 2.7.12 2024-04-05). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2024-04-05 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 2.7.
HAProxy 2.5 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2023-Q1 (unmaintained)' for branch 2.5 (latest 2.5.14 2023-05-02). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2023-05-02 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 2.5.
HAProxy 2.4 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2026-Q2 (unmaintained)' for branch 2.4 (latest 2.4.36 2026-07-03). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2026-04-01 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 2.4.
HAProxy 2.3 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2022-Q1 (unmaintained)' for branch 2.3 (latest 2.3.21 2022-07-27). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2022-07-27 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 2.3.
HAProxy 2.2 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2025-Q2 (unmaintained)' for branch 2.2 (latest 2.2.34 2025-04-23). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2025-04-23 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 2.2.
HAProxy 2.1 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2021-Q1 (unmaintained)' for branch 2.1 (latest 2.1.12 2021-03-18). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2021-03-18 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 2.1.
HAProxy 2.0 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2024-Q2 (unmaintained)' for branch 2.0 (latest 2.0.35 2024-04-05). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2024-04-05 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 2.0.
HAProxy 1.9 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2020-Q2 (unmaintained)' for branch 1.9 (latest 1.9.16 2020-07-31). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2020-07-31 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 1.9.
HAProxy 1.8 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2022-Q4 (unmaintained)' for branch 1.8 (latest 1.8.31 2022-12-09). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2022-12-09 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 1.8.
HAProxy 1.7 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2021-Q4 (unmaintained)' for branch 1.7 (latest 1.7.14 2021-03-31). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2021-10-01 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 1.7.
HAProxy 1.6 true vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2020-Q4 (unmaintained)' for branch 1.6 (latest 1.6.16 2021-03-19). The page states the policy only in years and quarters: 'Branches with an even number are called LTS (for long term support) and area maintained for 5 years after their release' and 'Branches with an odd number are only called stable ... These versions are maintained between 12 and 18 months'; the End of life column prints a quarter, never a day, for every branch from 1.6 up (upstream haproxy.md: 'This page takes a conservative approach, using the start of quarter as the EOL date'). Upstream serves 2020-10-01 (its own max of the quarter start and the last release day), a day HAProxy never printed as the end. Vendor floor rule: the quarter has passed and the branch is marked unmaintained, eol true, day not published. Pinned by sentinel haproxy-release-table. Retire when haproxy.org prints a day for 1.6.
HAProxy 1.4 2018-02-08 vendor source ↗ haproxy.org read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical). The table prints End of life '2018-02-08 (unmaintained)' for branch 1.4, one of the five branches (1.0 to 1.5) for which HAProxy prints a day. Upstream serves 2020-01-10, the day printed for 1.5, not 1.4. Pinned by sentinel haproxy-release-table. Retire when upstream serves 2018-02-08.
OPNsense 25.7 — vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 25.7: heading '25.7 (July 23, 2025)' (upstream releaseDate 2025-07-22). Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 25.1 — vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 25.1: heading '25.1 (January 29, 2025)' (upstream releaseDate 2025-01-28); heading '25.1.12 (July 22, 2025)' (upstream latestReleaseDate 2025-07-21). Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 24.7 2025-01-29 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 24.7: heading '24.7 (July 25, 2024)' (upstream releaseDate 2024-07-23); the next community release heading prints January 29, 2025 (upstream eol 2025-01-28); heading '24.7.12 (January 15, 2025)' (upstream latestReleaseDate 2025-01-14). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 24.1 — vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 24.1: heading '24.1 (January 30, 2024)' (upstream releaseDate 2024-01-26). Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 23.7 2024-01-30 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 23.7: heading '23.7 (July 31, 2023)' (upstream releaseDate 2023-07-28); the next community release heading prints January 30, 2024 (upstream eol 2024-01-26). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 23.1 2023-07-31 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 23.1: heading '23.1 (January 26, 2023)' (upstream releaseDate 2023-01-25); the next community release heading prints July 31, 2023 (upstream eol 2023-07-28); heading '23.1.11 (June 28, 2023)' (upstream latestReleaseDate 2023-06-27). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 22.7 2023-01-26 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 22.7: heading '22.7 (July 28, 2022)' (upstream releaseDate 2022-07-25); the next community release heading prints January 26, 2023 (upstream eol 2023-01-25); heading '22.7.11 (January 18, 2023)' (upstream latestReleaseDate 2023-01-17). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 22.1 2022-07-28 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 22.1: heading '22.1 (January 27, 2022)' (upstream releaseDate 2022-01-25); the next community release heading prints July 28, 2022 (upstream eol 2022-07-25); heading '22.1.10 (July 07, 2022)' (upstream latestReleaseDate 2022-07-06). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 21.7 2022-01-27 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 21.7: heading '21.7 (July 28, 2021)' (upstream releaseDate 2021-07-23); the next community release heading prints January 27, 2022 (upstream eol 2022-01-25). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 21.1 2021-07-28 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 21.1: heading '21.1 (January 28, 2021)' (upstream releaseDate 2021-01-26); the next community release heading prints July 28, 2021 (upstream eol 2021-07-23); heading '21.1.9 (July 27, 2021)' (upstream latestReleaseDate 2021-07-26). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 20.7 2021-01-28 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 20.7: heading '20.7 (July 30, 2020)' (upstream releaseDate 2020-07-28); the next community release heading prints January 28, 2021 (upstream eol 2021-01-26); heading '20.7.8 (January 19, 2021)' (upstream latestReleaseDate 2021-01-18). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 20.1 2020-07-30 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 20.1: heading '20.1 (January 30, 2020)' (upstream releaseDate 2020-01-29); the next community release heading prints July 30, 2020 (upstream eol 2020-07-28). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 19.7 2020-01-30 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 19.7: heading '19.7 (July 17, 2019)' (upstream releaseDate 2019-07-15); the next community release heading prints January 30, 2020 (upstream eol 2020-01-29). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 19.1 2019-07-17 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 19.1: heading '19.1 (January 31, 2019)' (upstream releaseDate 2019-01-28); the next community release heading prints July 17, 2019 (upstream eol 2019-07-15); heading '19.1.10 (July 03, 2019)' (upstream latestReleaseDate 2019-07-02). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 18.7 2019-01-31 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 18.7: heading '18.7 (July 31, 2018)' (upstream releaseDate 2018-07-29); the next community release heading prints January 31, 2019 (upstream eol 2019-01-28); heading '18.7.10 (January 07, 2019)' (upstream latestReleaseDate 2019-01-06). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 18.1 2018-07-31 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 18.1: heading '18.1 (January 29, 2018)' (upstream releaseDate 2018-01-26); the next community release heading prints July 31, 2018 (upstream eol 2018-07-29); heading '18.1.13 (July 24, 2018)' (upstream latestReleaseDate 2018-07-23). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 17.7 2018-01-29 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 17.7: heading '17.7 (July 31, 2017)' (upstream releaseDate 2017-07-26); the next community release heading prints January 29, 2018 (upstream eol 2018-01-26); heading '17.7.12 (January 18, 2018)' (upstream latestReleaseDate 2018-01-17). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 17.1 2017-07-31 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 17.1: heading '17.1 (January 31, 2017)' (upstream releaseDate 2017-01-27); the next community release heading prints July 31, 2017 (upstream eol 2017-07-26); heading '17.1.11 (July 25, 2017)' (upstream latestReleaseDate 2017-07-24). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 16.7 2017-01-31 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 16.7: heading '16.7 (July 28, 2016)' (upstream releaseDate 2016-07-26); the next community release heading prints January 31, 2017 (upstream eol 2017-01-27); heading '16.7.14 (January 25, 2017)' (upstream latestReleaseDate 2017-01-24). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
OPNsense 16.1 2016-07-28 vendor source ↗ docs.opnsense.org/releases/CE_<cycle>.html (the changelog headings print the day of every release) read 2026-10-11 two ways (curl with a browser User-Agent and the built-in browser, identical); the roadmap at opnsense.org/about/road-map/ prints the same major release day for every cycle except 23.1 (roadmap 13th January 2023, changelog January 26, 2023). For 16.1: the next community release heading prints July 28, 2016 (upstream eol 2016-07-26). Policy (github.com/opnsense/core SECURITY.md, read twice): 'For both the community and business edition only the last published major branches are supported in terms of security updates.' so a community branch ends on the day the next community release ships. Upstream days are one to five days earlier than any day the vendor prints (endoflife.date opnsense.md computes eol(x) = releaseDate(x+1) from its own release days). Pinned by sentinels opnsense-security-policy-last-published and opnsense-ce-25-1-release-day. Retire when upstream serves the vendor days.
Visual Studio 18.10 2026-10-13 vendor source ↗ vendor adapter visual-studio: Visual Studio 2026 release history lists 'Stable | 18.11.0 | October 13, 2026' (and the final 18.10 servicing release, 18.10.4, the same day); the servicing policy page (releases/2026/servicing-vs) says 'For Visual Studio 2026 and later, we do not offer support or servicing for older Visual Studio releases other than LTSC releases' and the Stable Channel is supported on the latest release, so 18.10 ended when 18.11 shipped. Upstream still serves false. Read twice 2026-10-14 (adapter run and a direct read of both pages).
WordPress 4.1 true vendor source ↗ WordPress Security Team (John Blackbourn, 2025-06-18): will cease providing updates for WordPress versions 4.1 to 4.6 in July 2025. No day is published; upstream 2025-07-31 is a month-end floor, so the line is served as ended without a date (vendor-floor-dates rule). Read 2026-10-15.
WordPress 4.2 true vendor source ↗ WordPress Security Team (John Blackbourn, 2025-06-18): will cease providing updates for WordPress versions 4.1 to 4.6 in July 2025. No day is published; upstream 2025-07-31 is a month-end floor, so the line is served as ended without a date (vendor-floor-dates rule). Read 2026-10-15.
WordPress 4.3 true vendor source ↗ WordPress Security Team (John Blackbourn, 2025-06-18): will cease providing updates for WordPress versions 4.1 to 4.6 in July 2025. No day is published; upstream 2025-07-31 is a month-end floor, so the line is served as ended without a date (vendor-floor-dates rule). Read 2026-10-15.
WordPress 4.4 true vendor source ↗ WordPress Security Team (John Blackbourn, 2025-06-18): will cease providing updates for WordPress versions 4.1 to 4.6 in July 2025. No day is published; upstream 2025-07-31 is a month-end floor, so the line is served as ended without a date (vendor-floor-dates rule). Read 2026-10-15.
WordPress 4.5 true vendor source ↗ WordPress Security Team (John Blackbourn, 2025-06-18): will cease providing updates for WordPress versions 4.1 to 4.6 in July 2025. No day is published; upstream 2025-07-31 is a month-end floor, so the line is served as ended without a date (vendor-floor-dates rule). Read 2026-10-15.
WordPress 4.6 true vendor source ↗ WordPress Security Team (John Blackbourn, 2025-06-18): will cease providing updates for WordPress versions 4.1 to 4.6 in July 2025. No day is published; upstream 2025-07-31 is a month-end floor, so the line is served as ended without a date (vendor-floor-dates rule). Read 2026-10-15.

Corrections policy

A date on this site changes only when the vendor's own page says so. Before we change a served date by hand, we read the vendor's lifecycle page twice and the two reads must agree; a blog post, a mirror or an AI answer is never a source. Every correction is recorded with the day it was made, the value we served before, the value we serve now and the vendor page it came from, and appears on the change record, which lists the last 180 days. When the community dataset we build on moves a date by a year or more, drops a date or removes a version, that change is held and the last value keeps serving until a person has checked the vendor's page. The share of dates read at the vendor, the rate at which independent sources agree and every open disagreement are on this page, recomputed at every build. If you find a date we show that the vendor's page contradicts, tell us with the form below or by email to [email protected]. Each report is checked against the vendor page named in it; a report the vendor's page confirms becomes a correction on the change record, with its source.

Report a correction

The vendor's own lifecycle page is the one thing we need; a link to it is required. Your email is optional and is used only to tell you what the check found.

✓ Report received. It will be checked against the vendor page you gave. A report the vendor's page confirms becomes a correction on the change record.

Vendor-verified products

Each product below was checked against the linked official vendor lifecycle page on the date shown. Verified products display a ✓ provenance line on their pages.

ProductChecked againstLast checked
Adobe Acrobat Adobe ↗ 2026-10-10
Adobe Experience Manager Adobe ↗ 2026-10-10
AlmaLinux AlmaLinux OS Foundation ↗ 2026-09-24
Alpine Linux Alpine Linux ↗ 2026-10-09
Amazon Corretto Amazon Web Services ↗ 2026-09-24
Angular Google (Angular team) ↗ 2026-10-01
AngularJS Google (AngularJS team) ↗ 2026-09-28
Ansible Ansible project (Red Hat) ↗ 2026-10-07
Ansible Core Ansible project (Red Hat) ↗ 2026-10-07
Apache HTTP Server Apache Software Foundation (HTTP Server Project) ↗ 2026-09-24
Arista EOS Arista ↗ 2026-10-09
Azul Zulu Azul Systems ↗ 2026-09-24
Barracuda CloudGen Firewall Barracuda Networks ↗ 2026-10-10
Barracuda Web Application Firewall Barracuda Networks ↗ 2026-10-10
CentOS CentOS Project ↗ 2026-10-01
CentOS Stream CentOS Project ↗ 2026-09-21
Check Point security gateway appliances (hardware) Check Point Software Technologies ↗ 2026-10-11
Cisco IOS Cisco ↗ 2026-10-09
Cisco IOS XE Cisco ↗ 2026-10-06
Cisco Meraki Cisco Meraki ↗ 2026-10-10
Cisco NX-OS Cisco ↗ 2026-10-09
XenServer (Citrix Hypervisor) Cloud Software Group (XenServer) ↗ 2026-10-10
Citrix Workspace app Citrix ↗ 2026-10-10
CloudLinux OS CloudLinux ↗ 2026-10-09
Confluence Atlassian ↗ 2026-10-06
Confluent Platform Confluent ↗ 2026-10-09
Consul HashiCorp ↗ 2026-10-07
Debian Debian Project ↗ 2026-10-06
Django Django Software Foundation ↗ 2026-09-24
.NET Microsoft ↗ 2026-09-17
Eclipse Temurin Eclipse Adoptium ↗ 2026-09-24
VMware ESXi Broadcom (VMware) ↗ 2026-09-21
Fedora Fedora Project ↗ 2026-10-01
FortiNAC Fortinet ↗ 2026-10-07
FortiNAC-F Fortinet ↗ 2026-10-08
Go Go project (Google) ↗ 2026-09-21
IBM Db2 IBM ↗ 2026-10-06
IBM WebSphere Application Server IBM ↗ 2026-10-09
Ivanti Endpoint Manager Mobile (EPMM) Ivanti ↗ 2026-10-10
Ivanti Sentry Ivanti ↗ 2026-10-10
Juniper EX Series (hardware) Juniper Networks ↗ 2026-10-11
Juniper MX and M Series (hardware) Juniper Networks ↗ 2026-10-11
Juniper QFX Series (hardware) Juniper Networks ↗ 2026-10-11
Kaseya VSA Kaseya ↗ 2026-10-09
Kubernetes Kubernetes (CNCF) ↗ 2026-09-17
Linux Linux Kernel Organization (kernel.org) ↗ 2026-09-28
Linux Mint Linux Mint ↗ 2026-09-28
Magento Adobe ↗ 2026-10-06
ManageEngine Endpoint Central ManageEngine (Zoho) ↗ 2026-10-10
MariaDB MariaDB Foundation ↗ 2026-09-21
BizTalk Server Microsoft ↗ 2026-10-09
Microsoft Configuration Manager Microsoft ↗ 2026-10-09
Dynamics AX Microsoft ↗ 2026-10-09
Dynamics 365 Business Central on-premises Microsoft ↗ 2026-10-09
Dynamics CRM Microsoft ↗ 2026-10-09
Dynamics 365 Customer Engagement (on-premises) Microsoft ↗ 2026-10-09
Dynamics GP Microsoft ↗ 2026-10-09
Dynamics NAV Microsoft ↗ 2026-10-09
Dynamics SL Microsoft ↗ 2026-10-09
Microsoft Entra Connect Microsoft ↗ 2026-10-09
Microsoft Hyper-V Server Microsoft ↗ 2026-10-11
Skype for Business Server Microsoft ↗ 2026-10-09
System Center Microsoft ↗ 2026-10-09
MongoDB MongoDB, Inc. ↗ 2026-09-24
Microsoft Exchange Microsoft ↗ 2026-09-21
Microsoft SQL Server Microsoft ↗ 2026-09-17
Node.js OpenJS Foundation / Node.js Release Working Group ↗ 2026-09-17
Nomad HashiCorp ↗ 2026-10-07
OpenJDK builds from Oracle Oracle (OpenJDK builds, jdk.java.net) ↗ 2026-09-24
OpenSSL OpenSSL Library ↗ 2026-09-21
Oracle ADF Oracle ↗ 2026-10-09
Oracle Database Oracle ↗ 2026-09-10
Oracle E-Business Suite Oracle ↗ 2026-10-09
Oracle Endeca Oracle ↗ 2026-10-11
Oracle Forms and Reports Oracle ↗ 2026-10-09
Oracle HTTP Server Oracle ↗ 2026-10-09
Oracle Identity and Access Management Oracle ↗ 2026-10-11
Oracle JDK Oracle ↗ 2026-09-17
Oracle PeopleSoft Oracle ↗ 2026-10-09
Oracle SOA Suite Oracle ↗ 2026-10-09
Oracle User Productivity Kit (UPK) Oracle ↗ 2026-10-11
PHP The PHP Group ↗ 2026-09-17
PostgreSQL PostgreSQL Global Development Group ↗ 2026-09-17
Progress LoadMaster Progress Software (Kemp Technologies) ↗ 2026-10-11
Progress MOVEit Automation Progress ↗ 2026-10-09
Progress MOVEit Transfer Progress ↗ 2026-10-09
Progress WhatsUp Gold Progress ↗ 2026-10-09
Progress WS_FTP Server Progress ↗ 2026-10-09
Python Python Software Foundation ↗ 2026-09-17
QNAP NAS QNAP ↗ 2026-10-07
Red Hat OpenShift Red Hat ↗ 2026-10-06
Red Hat OpenStack Platform Red Hat ↗ 2026-10-09
Red Hat Virtualization Red Hat ↗ 2026-10-09
Redis Redis Ltd. ↗ 2026-10-01
RHEL Red Hat ↗ 2026-09-17
Rocky Linux Rocky Enterprise Software Foundation ↗ 2026-09-24
Ruby Ruby core team (ruby-lang.org) ↗ 2026-09-21
Rust Rust project ↗ 2026-09-21
SAP BusinessObjects BI SAP ↗ 2026-10-10
SAP NetWeaver SAP ↗ 2026-10-10
SharePoint Microsoft ↗ 2026-09-21
SolarWinds Orion Platform SolarWinds ↗ 2026-10-09
SolarWinds Serv-U SolarWinds ↗ 2026-10-09
SolarWinds Web Help Desk SolarWinds ↗ 2026-10-09
SonicWall Network Security Manager (NSM) On-Prem SonicWall ↗ 2026-10-11
SonicWall SonicWave / SonicPoint access points (hardware) SonicWall ↗ 2026-10-11
Spring Boot Broadcom (Spring / VMware Tanzu) ↗ 2026-09-24
Spring Framework Broadcom (Spring / VMware Tanzu) ↗ 2026-09-24
Synology DSM Synology ↗ 2026-10-10
Thymeleaf Thymeleaf ↗ 2026-10-08
Apache Tomcat Apache Software Foundation (Tomcat Project) ↗ 2026-09-17
Trend Micro Apex Central Trend Micro ↗ 2026-10-10
Trend Micro Apex One Trend Micro ↗ 2026-10-10
Ubiquiti UniFi Ubiquiti ↗ 2026-10-10
Ubuntu Canonical ↗ 2026-09-17
Veeam Backup & Replication Veeam ↗ 2026-09-21
Veeam Backup for Microsoft 365 Veeam ↗ 2026-10-06
VMware Aria Automation Broadcom (VMware) ↗ 2026-10-10
VMware Aria Operations Broadcom (VMware) ↗ 2026-10-10
VMware NSX Broadcom (VMware) ↗ 2026-10-10
VMware Tools Broadcom (VMware) ↗ 2026-10-10
Vue.js Vue.js team (Evan You / Vue core team) ↗ 2026-09-28
Windows Microsoft ↗ 2026-09-24
Windows Server Microsoft ↗ 2026-09-17
Windows Server Core Microsoft ↗ 2026-09-21
Zabbix Zabbix ↗ 2026-10-06
Zerto HPE Zerto ↗ 2026-10-07

Honestly unconfirmed

Some projects publish support policies but no per-version dates (React, Docker Engine, NGINX, GitLab, Jenkins, WordPress). Dates we show for them are policy-derived and labeled accordingly — we do not claim vendor verification we can't demonstrate.

Methodology

Verification means a human-reviewed comparison of our published dates against the vendor's own lifecycle documentation — not a blog post, not a mirror, the primary source. Base data comes from the open-source endoflife.date project plus vendor lifecycle pages; risk scores, verification, and corrections are our own layer. Verification coverage expands in ongoing batches, prioritized by product impact. Found an error? Report a correction with the vendor page that shows it (see the corrections policy) — or check any date yourself with the EOL Checker.