Dependency health lifecycles

Published support dates

Product lifecycles

Know when support ends, before it becomes an emergency.

473 products · Daily refresh at 02:30 UTC
Last successful collection: 2026-09-11 15:31 UTC
Source snapshot: 2026-09-11 14:51 UTC

Ansible-core

Release lineStatusEnd of active supportEnd of lifeEnd of extended supportLatest in line
2.21Not end of lifeNot recorded2027-11-30Not recorded2.21.4
2.20Not end of lifeNot recorded2027-05-31Not recorded2.20.9
2.19Not end of lifeNot recorded2026-11-30Not recorded2.19.13
2.18End of lifeNot recorded2026-05-31Not recorded2.18.19
2.17End of lifeNot recorded2025-11-30Not recorded2.17.14
2.16End of lifeNot recorded2025-07-31Not recorded2.16.19
2.15End of lifeNot recorded2024-11-30Not recorded2.15.13
2.14End of lifeNot recorded2024-05-20Not recorded2.14.18
2.13End of lifeNot recorded2023-11-06Not recorded2.13.13
2.12End of lifeNot recorded2023-05-22Not recorded2.12.10
2.11End of lifeNot recorded2022-11-07Not recorded2.11.12
2.10End of lifeNot recorded2022-05-23Not recorded2.10.17
2.9End of lifeNot recorded2022-05-23Not recorded2.9.27

endoflife.date evidence ↗ · Maintainer policy ↗

Extended support may require a paid agreement. A recorded date does not establish your entitlement. Missing dates do not mean indefinite support; a maintained product can still have unsupported release lines.

Source: endoflife.date · MIT licence. Data is normalised for display. Published lifecycle evidence is separate from our inferred package-maintenance verdicts and vulnerability checks. Product coverage does not imply that every package or SBOM component has a verified product mapping.