# Ansible 12 lifecycle?

**URL:** <https://forum.ansible.com/t/ansible-12-lifecycle/44977>\
**Category:** Project Discussions\
**Tags:** community-wg\
**Created:** [December 9, 2025, 5:55pm UTC](https://forum.ansible.com/t/ansible-12-lifecycle/44977 "2025-12-09T17:55:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [December 9, 2025, 5:55pm UTC](https://forum.ansible.com/t/ansible-12-lifecycle/44977/1 "2025-12-09T17:55:33Z")

</div>

Ansible 12 is technically supposed to go EOL with today’s release even though Core was delayed and Ansible 12 was only GA for three months, instead of the usual six months. I wonder if we should extend for the usual six months until shortly after the end of the Ansible Core bugfix maintenance phase like we usually do.

[Releases and maintenance — Ansible Core Documentation](https://docs.ansible.com/projects/ansible-core/devel/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix) currently lists Core 2.19’s dates as `GA: 21 July 2025` and `Critical: 03 Nov 2025`, but I’m not sure if the Critical date will also be pushed back since the GA was so late. [@Core](https://forum.ansible.com/groups/core), what are the plans for 2.19’s support lifecycle?

If the Core bugfix support lifecycle is also going to be extended, I think we should definitely follow suit. Otherwise, I am more open to also cutting Ansible 12’s GA lifecycle short.

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [December 9, 2025, 6:24pm UTC](https://forum.ansible.com/t/ansible-12-lifecycle/44977/2 "2025-12-09T18:24:27Z")

</div>

There are no plans to change the dates of core 2.19, it will EOL as planned, regardless of the GA delay.

---

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [December 9, 2025, 6:47pm UTC](https://forum.ansible.com/t/ansible-12-lifecycle/44977/3 "2025-12-09T18:47:45Z")

</div>

So to confirm, Core 2.19 is now in the critical bugfix only phase, right?

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [December 9, 2025, 8:47pm UTC](https://forum.ansible.com/t/ansible-12-lifecycle/44977/4 "2025-12-09T20:47:02Z")

</div>

I was pretty sure we already discussed somewhen earlier this year that Ansible 12 will still be EOL now, but I cannot find it anymore… (ETOOMANYDISCUSSIONS)

---

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [December 10, 2025, 1:29pm UTC](https://forum.ansible.com/t/ansible-12-lifecycle/44977/5 "2025-12-10T13:29:02Z")

</div>

For the record, the release managers decided on Matrix to go ahead with marking the Ansible 11 and 12 releases from yesterday as EOL based on the current roadmaps.
