Requirement
The collection currently states a different minimum supported Ansible-core version in different
places (docs vs. meta/runtime.yml's enforced requires_ansible vs. the CI test matrix vs.
tox.ini) — these need to agree with each other, and with what Red Hat's Automation Hub partner
certification tooling will actually test.
Specifically: Red Hat's partner-certification-checker v3.0.0 (released July 2026) bumped its
own minimum Ansible-core requirement to >=2.16.0 and fixed its sanity-test matrix to
stable-2.16 / stable-2.18 / stable-2.20. Whatever floor we land on needs to be at least that,
or certification will flag it regardless of what we've internally decided is "supported."
Python's minimum should follow from whichever Ansible-core floor is chosen (each Ansible-core
release has its own Python floor), rather than being stated independently, since that's the actual
source of the constraint.
Compatibility approach for older Ansible-core versions
Ansible-core versions older than the certification checker's floor are not required to be tested or
verified — compatibility with them is a nice-to-have, not a requirement. Recommend aligning the
enforced floor and CI matrix to the checker's floor (>=2.16.0) as outlined above.
Reference (not a spec — context from reading the repo, not a required approach)
Four places currently disagree: README.md ("tested >= 2.12"), meta/runtime.yml
(requires_ansible: ">=2.15.0" — the one actually enforced at install/run time), the CI units test
matrix (stable-2.10 through stable-2.16), and tox.ini (2.15–2.18). How you consolidate these —
one file driving the others, or something else that fits your existing CI setup better — is your
call.
Requirement
The collection currently states a different minimum supported Ansible-core version in different
places (docs vs.
meta/runtime.yml's enforcedrequires_ansiblevs. the CI test matrix vs.tox.ini) — these need to agree with each other, and with what Red Hat's Automation Hub partnercertification tooling will actually test.
Specifically: Red Hat's
partner-certification-checkerv3.0.0 (released July 2026) bumped itsown minimum Ansible-core requirement to
>=2.16.0and fixed its sanity-test matrix tostable-2.16/stable-2.18/stable-2.20. Whatever floor we land on needs to be at least that,or certification will flag it regardless of what we've internally decided is "supported."
Python's minimum should follow from whichever Ansible-core floor is chosen (each Ansible-core
release has its own Python floor), rather than being stated independently, since that's the actual
source of the constraint.
Compatibility approach for older Ansible-core versions
Ansible-core versions older than the certification checker's floor are not required to be tested or
verified — compatibility with them is a nice-to-have, not a requirement. Recommend aligning the
enforced floor and CI matrix to the checker's floor (
>=2.16.0) as outlined above.Reference (not a spec — context from reading the repo, not a required approach)
Four places currently disagree:
README.md("tested >= 2.12"),meta/runtime.yml(
requires_ansible: ">=2.15.0"— the one actually enforced at install/run time), the CI units testmatrix (
stable-2.10throughstable-2.16), andtox.ini(2.15–2.18). How you consolidate these —one file driving the others, or something else that fits your existing CI setup better — is your
call.