# Ansible.netcommon broken with Ansible Core 2.19.0

**URL:** <https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043>\
**Category:** Get Help\
**Tags:** cisco, templating, network\
**Created:** [July 23, 2025, 6:46pm UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043 "2025-07-23T18:46:00Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [July 29, 2025, 3:18pm UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/13 "2025-07-29T15:18:01Z")

</div>

For the record, we discussed [making Ansible 11 a “LTS” (similar to Ansible 9)](https://forum.ansible.com/t/40851) because of the changes introduced by Data Tagging in ansible-core 2.19. Long story short: We will provide minor and patch releases for 6 months longer, until Ansible 13 is released.

For people using the Ansible Community Package instead of ansible-core plus selected collections, this might make the decision easier if Ansible 11 is still an option. It will not be EOL once Ansible 12 is released, as originally planned!

---

_[View the full topic](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043)._
