ShutdownRadar
Support lifecycle

ansible end of life dates — full support timeline

13 of 14 tracked ansible releases have already reached end of life. The dates below are published support dates, not estimates.

Version support timeline

ReleaseReleasedEnd of lifeLatestStatus
142026-06-02not announced14.2.0supported
132025-11-192026-06-1813.8.0ended
122025-09-092025-12-0912.3.0ended
112024-11-192025-12-0911.13.0ended
102024-06-042024-12-0310.7.0ended
92023-11-212024-12-039.13.0ended
82023-05-302023-12-068.7.0ended
72022-11-222023-06-227.7.0ended
62022-06-212022-12-066.7.0ended
52021-12-022022-06-085.10.0ended
42021-05-182021-12-144.10.0ended
32021-02-182021-05-113.4.0ended
2.102020-09-222021-02-092.10.7ended
2.92019-10-312022-05-232.9.27ended

Who is affected

Anyone running an unsupported ansible release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.

Source

These dates are maintained by endoflife.date/ansible, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.

Get told before the next ansible deadline

You are reading this because a ansible release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every ansible and related deadline as it is announced, with exact dates and primary sources.

Watch ansible deadlines Team monitoring pilot →

Takes about twenty seconds. No account, no card, no tracking.

All upcoming deadlines · Full archive