EOL.Wiki EOL.Wiki
← ← Back to all products

Ansible

Active
DevOps & CI/CD Latest Version: 13.3.0 Latest Release: Jan 29, 2026

Ansible is an open-source automation tool for configuration management, application deployment, and orchestration.

Versions

13

Latest Version

13.3.0

Active Support

1

EOL

12

Lifecycle Timeline

Today
13
13
12
12
11
11
10
10
9
9
8
8
7
7
6
6
5
5
4
4
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
13Nov 19, 2025-No13.3.0No
Active
12Sep 9, 2025-Dec 9, 202512.3.0No
EOL
11Nov 19, 2024-Dec 9, 202511.13.0No
EOL
10Jun 4, 2024-Dec 3, 202410.7.0No
EOL
9Nov 21, 2023-Dec 3, 20249.13.0No
EOL
8May 30, 2023-Dec 6, 20238.7.0No
EOL
7Nov 22, 2022-Jun 22, 20237.7.0No
EOL
6Jun 21, 2022-Dec 6, 20226.7.0No
EOL
5Dec 2, 2021-Jun 8, 20225.10.0No
EOL
4May 18, 2021-Dec 14, 20214.10.0No
EOL
3Feb 18, 2021-May 11, 20213.4.0No
EOL
2.10Sep 22, 2020-Feb 9, 20212.10.7No
EOL
2.9Oct 31, 2019-May 23, 20222.9.27No
EOL

Frequently Asked Questions

Which versions of Ansible have reached end of life?
The following Ansible versions have reached end of life and no longer receive security updates: 12, 11, 10, 9, 8, 7, 6, 5 (and 4 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Ansible 12?
Ansible 12 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 Ansible?
The latest version of Ansible is 13.3.0, released in the 13 release cycle.
How many versions of Ansible are currently supported?
Ansible currently has 1 actively supported version(s): 13.
When does Ansible 13 reach end of life?
Ansible 13 does not have a specific end-of-life date announced yet.
What should I do when Ansible reaches end of life?
When a Ansible 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.