# Ansible.netcommon broken with Ansible Core 2.19.0 **URL:** \ **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:** 11\ **Page:** 2
**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 12, 2025, 9:04am UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/21 "2025-08-12T09:04:25Z")
The concerned [PRs](https://github.com/ansible-collections/ansible.netcommon/pull/711) are merged, and we are planning to push a release by Thursday (Aug 14) While we are planning the release, I would like to thank @mattclay @nitzmahone @Ruchi_Pakhle @gundalow @komal for all the help and support in getting things fixed and running. Regards ---
**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 14, 2025, 3:20pm UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/22 "2025-08-14T15:20:04Z")
ansible.netcommon v8.1.0 is released 🎉 The underlying network platform collections would have a iteration of major releases to update the known dependency (planned next week) Regards. ---
**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:** [August 14, 2025, 3:51pm UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/23 "2025-08-14T15:51:34Z")
@KB-perByte I’m not quite sure what this means. Does ansible.netcommon v8.1.0 fix the issues with ansible-core 2.19.0, or will the collection be compatible with ansible-core 2.19.1+ only? I’m sorry if you’ve already answered this somewhere else. I wasn’t able to find this ☹ BTW the [meta/runtime.yml](https://github.com/ansible-collections/ansible.netcommon/blob/v8.1.0/meta/runtime.yml) states `requires_ansible: ">=2.16.0"`. Out of curiosity: If the collection will be compatible with 2.19.1 but _not_ 2.19.0, would there be a way to define this? Something like `requires_ansible: ">=2.16.0;!2.19.0"` or similar? ---
**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:** [August 14, 2025, 6:47pm UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/24 "2025-08-14T18:47:19Z")
@KB-perByte why are you bumping major versions for the network collections? I checked [prep release 11.0.0 by KB-perByte · Pull Request #1225 · ansible-collections/cisco.ios · GitHub](https://github.com/ansible-collections/cisco.ios/pull/1225/files) as an example, and I see **zero** reason to make a major version bump. The only changes seem to be a bugfix and a dependency bump, which can both be done in a minor release. Same for [prep release 12.0.0 by KB-perByte · Pull Request #559 · ansible-collections/cisco.iosxr · GitHub](https://github.com/ansible-collections/cisco.iosxr/pull/559/files), there’s no reason to make this a new major release. Please reconsider and make minor releases! ---
**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:** [August 15, 2025, 3:16pm UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/25 "2025-08-15T15:16:20Z")
> [@felixfontein](#): > > a dependency bump, which can both be done in a minor release Is is really acceptable to do a dependency bump to anothor _major_ version in a new _minor_ version? I’m always unsure about this and try to avoid it. Anyway, I’m not even sure if this dependency bump is really necessary. I’ve commented in the PRs. ---
**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:** [August 15, 2025, 4:51pm UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/26 "2025-08-15T16:51:12Z")
I think it’s OK (that doesn’t say anything about whether it’s a good idea), since the package manager (ansible-galaxy) has a resolver that takes care of dependencies. Whether it’s a good idea: I agree with you that it’s not necessary, and I personally wouldn’t do it either. Bumping the minimum required dependency version without this being really required only makes it harder for many users who cannot update to that dependency for whatever reason. Also ansible-galaxy is still missing some important features, like making use of `requires_ansible` (that was originally planned for ansible-core 2.19, but got moved to later), which can make this bump more problematic for users if ansible.netcommon drops support for ansible-core versions with that bump. ---
**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")
@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 ---
**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:** [August 18, 2025, 7:53pm UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/28 "2025-08-18T19:53:03Z")
I still don’t get why a **major** release is needed for this. A minor release would be fine as well? ---
**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:** [August 21, 2025, 6:56pm UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/29 "2025-08-21T18:56:13Z")
We just released Ansible 12.0.0b4 which includes the new ansible.netcommon releases as well as the new network collection releases. Would be great if everyone who has appropriate hardware can help taking a look whether the issues have been resolved! ---
**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 22, 2025, 7:03am UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/30 "2025-08-22T07:03:10Z")
Thank you! Someone from my team can help confirm that @felixfontein CC @rohitthakur2590 @chetna ---
**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\ **Post date:** [September 21, 2025, 7:03am UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/31 "2025-09-21T07:03:20Z")
Closed on September 21, 2025, 7:03am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed. [Previous page](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043.md?page=1)