So they are testing against what is currently the core version in Ansible community package 11, and will not be tested for the core version for what will be Ansible community package 12. So yeah, feels like if it’s not breaking any rules, they should be deprecated asap so we can remove in Ansible community package 12.
It would help if @network-wg would make clear that they will not support ansible-core > 2.17. I think “compatibility with ansible-core versions >2.17 will not be guaranteed” is a little bit unclear.
@samccann@mariolenz The Ansible Network team is okay with deprecating these collections from Ansible 11 and removing them in Ansible 12. Please let us know if there’s anything needed from our side. Thank you!
Ansible 10 is based on ansible-core 2.17, which the collections tests against. Ansible 11 will be based on ansible-core 2.18, which the collections do no longer test against, if I understood correctly.
@nilashishc I’m not sure if this is really supported and would work, but maybe you should change requires_ansible: ">=2.9.10" in meta/runtime.yml to requires_ansible: ">=2.9.10,<2.18.0"
@mariolenz There’s a possibility of vyos.vyos being taken up by another set of maintainers. We’re currently in discussions regarding that. This is why I’ve not made the same meta/runtime.yml change in it.