# 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:** 27

<div class="post-metadata">

**Author:** ![KB-perByte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kb-perbyte/32/541_2.png) [@KB-perByte](https://forum.ansible.com/u/KB-perByte)\
**Post date:** [August 18, 2025, 6:40am UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/27 "2025-08-18T06:40:35Z")

</div>

@felixfontein @mariolenz The concern is real. But we need to bump the dependency to make sure that the platform collection always resolves aka pulls in the correct version of netcommon, to support all versions of ansible-core that we are testing with that is 2.15 - 2.19 and devel, milestone.

Now,

- **Core ≤ 2.18**

- **Core = 2.19**

- **Core = 2.19 + `netcommon` v8.1.0 (released)**

- **Resolution**

We recommend doing major releases if we are dealing with breaking changes. Now, most of our customers/ community hooks into the latest releases of the collections anyways to address bug fixes and optimisation that goes in.

Regards

---

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