Ansible End of Life Dates
Release, end of support and end of life dates for every tracked Ansible version, with current status.
All products | Vendor lifecycle page | Source entry
Coverage note: some values are retained from earlier reviews. Unresolved releases or dates may be omitted; feed retrieval is not verification of every displayed value.
Status calculated for 2026-11-04: 14 versions tracked; 1 supported, 0 security fixes only, 0 ending within 90 days, 13 end of life. Calculated from the dates stored here, not a vendor verification date. With JavaScript on, the calculation uses today's date.
Swipe the table sideways to see all columns ->
| Version | Status | Released | Support ends | Latest |
|---|---|---|---|---|
| 14 | Supported | 2026-06-02 | Not announced | 14.6.0 |
| 13 | End of life | 2025-11-19 | 2026-06-18 | 13.8.0 |
| 12 | End of life | 2025-09-09 | 2025-12-09 | 12.3.0 |
| 11 | End of life | 2024-11-19 | 2025-12-09 | 11.13.0 |
| 10 | End of life | 2024-06-04 | 2024-12-03 | 10.7.0 |
| 9 | End of life | 2023-11-21 | 2024-12-03 | 9.13.0 |
| 8 | End of life | 2023-05-30 | 2023-12-06 | 8.7.0 |
| 7 | End of life | 2022-11-22 | 2023-06-22 | 7.7.0 |
| 6 | End of life | 2022-06-21 | 2022-12-06 | 6.7.0 |
| 5 | End of life | 2021-12-02 | 2022-06-08 | 5.10.0 |
| 4 | End of life | 2021-05-18 | 2021-12-14 | 4.10.0 |
| 3 | End of life | 2021-02-18 | 2021-05-11 | 3.4.0 |
| 2.10 | End of life | 2020-09-22 | 2021-02-09 | 2.10.7 |
| 2.9 | End of life | 2019-10-31 | 2022-05-23 | 2.9.27 |
Frequently asked questions
Which Ansible versions are still supported?
Using the dates stored here, status calculated for 2026-11-04 shows 1 of 14 tracked Ansible versions are still in support (14). The table above shows the calculated status of every tracked version; retained values may still need vendor confirmation.
What is the newest Ansible version tracked here?
14 (latest update 14.6.0), released 2026-06-02. This is the newest release included here, not necessarily the newest vendor release. Unresolved releases may be omitted while their dates or support status are checked. See the linked vendor source for current releases.
Where do these Ansible dates come from?
From the vendor sources linked at the top of this page (vendor lifecycle page) and the source entry. Vendors can revise dates, so confirm there before you schedule a migration.
Planning notes
Ansible ships two things with different maintenance rules. The Ansible community package is maintained for only one major release at a time: when a new major version ships, the team stops making new releases of the previous one. The separate ansible-core engine is maintained for the latest version plus two older ones.
That is why community package versions show as unmaintained so quickly in the table above. The project warns that an unmaintained community package release may carry unfixed security vulnerabilities, and recommends upgrading as soon as you can.
Check which of the two you actually run with `ansible --version` and `pip show ansible`. Each community package release pairs with a specific ansible-core version, so test your playbooks and collections against the new pair on a non-production host before you upgrade your control node.
Sources: Ansible release and maintenance.
Note: "Not announced" means no confirmed date is shown here; check the linked vendor source. "Ended (no date published)" means the source marks it ended without a date. Dates are compared as calendar days in your own time zone. A published end date counts as the last day of support.
Data: endoflife.date (MIT license), feed retrieved 2026-11-04. Retrieval does not mean every displayed value was verified that day. Some values are retained from earlier reviews, and unresolved releases or dates may be omitted. Confirm with the linked vendor source before a purchase or migration decision.