Argo Workflows — support and end-of-life dates
Argo Workflows 4.1 is the current release, released 2026-08-11, with no end-of-life date published upstream.
- 5 of its 7 tracked cycles have passed their EOL date (earliest tracked cycle 3.3)
Direct answer
Argo Workflows 4.1 has no published end-of-life date. Data as of 2026-11-18.
All tracked cycles
| Cycle | Released | Active support ends | End of life (EOL) | Latest | Status |
|---|---|---|---|---|---|
| 4.1 | 2026-08-11 | — | not announced | 4.1.6 | No EOL date |
| 4.0 | 2026-02-04 | — | not announced | 4.0.15 | No EOL date |
| 3.7 | 2025-07-23 | — | 2026-08-14 96 days ago | 3.7.18 | End of life |
| 3.6 | 2024-11-14 | — | 2026-02-04 287 days ago | 3.6.19 | End of life |
| 3.5 | 2023-10-13 | — | 2025-07-23 483 days ago | 3.5.15 | End of life |
| 3.4 | 2022-09-18 | — | 2024-11-14 734 days ago | 3.4.18 | End of life |
| 3.3 | 2022-03-14 | — | 2023-10-13 1132 days ago | 3.3.10 | End of life |
Upgrade path stated in the data
- No successor is stated in the upstream data for this product.
This is not a recommendation from DeprecateWatch. It repeats what the upstream source states, plus the newest cycle that is still inside its published support window.
Questions this page answers
Is Argo Workflows 4.1 end of life?
No. Argo Workflows 4.1 has no published end-of-life date in the source data.
How many Argo Workflows versions are already end of life?
5 of the 7 cycles tracked here have passed their EOL date as of 2026-11-18.
Other Server applications with upcoming deadlines
- GitLab — next EOL 2026-11-19 (19.3)
- GitLab Runner — next EOL 2026-11-19 (19.3)
- Bamboo — next EOL 2026-11-20 (10.1)
- Jira Service Management — next EOL 2026-11-20 (10.2)
- Jira Software — next EOL 2026-11-20 (10.2)
- Apache Spark — next EOL 2026-11-23 (4.0)
- Discourse — next EOL 2026-11-24 (2026.9)
- Longhorn — next EOL 2026-11-27 (1.9)
Source for the cycle table: endoflife.date/argo-workflows
read through the endoflife.date API on 2026-11-18. Machine-readable copy:
/api/eol.json (product key argo-workflows).