← ← Back to all products
Argo Workflows
Active
DevOps & CI/CD Latest Version: 4.0.0 Latest Release: Feb 4, 2026
Argo Workflows is a container-native workflow engine for orchestrating parallel jobs on Kubernetes.
Versions
6
Latest Version
4.0.0
Active Support
2
EOL
4
Lifecycle Timeline
Today ↓
4.0
4.0
3.7
3.7
3.6
3.6
3.5
3.5
3.4
3.4
3.3
3.3
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 4.0 | Feb 4, 2026 | - | No | 4.0.0 | No | Active |
| 3.7 | Jul 23, 2025 | - | No | 3.7.9 | No | Active |
| 3.6 | Nov 14, 2024 | - | Feb 4, 2026 | 3.6.18 | No | EOL |
| 3.5 | Oct 13, 2023 | - | Jul 23, 2025 | 3.5.15 | No | EOL |
| 3.4 | Sep 18, 2022 | - | Nov 14, 2024 | 3.4.18 | No | EOL |
| 3.3 | Mar 14, 2022 | - | Oct 13, 2023 | 3.3.10 | No | EOL |
Frequently Asked Questions
Which versions of Argo Workflows have reached end of life?
The following Argo Workflows versions have reached end of life and no longer receive security updates: 3.6, 3.5, 3.4, 3.3. It is recommended to upgrade to a supported version.
Is it safe to continue using Argo Workflows 3.6?
Argo Workflows 3.6 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Argo Workflows?
The latest version of Argo Workflows is 4.0.0, released in the 4.0 release cycle.
How many versions of Argo Workflows are currently supported?
Argo Workflows currently has 2 actively supported version(s): 4.0, 3.7.
When does Argo Workflows 4.0 reach end of life?
Argo Workflows 4.0 does not have a specific end-of-life date announced yet.
What should I do when Argo Workflows reaches end of life?
When a Argo Workflows version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.