As a user
Supported ansible-core versions when installing collections
Latest developments
None that I know of.
This wasn’t discussed at CfgMgmtCamp 2026.
Original text
Right now ansible-galaxy collection install’s dependency resolver still does not consider requires_ansible from meta/runtime.yml when installing collections. requires_ansible does declare which ansible-core (or ansible-base 2.10 / Ansible 2.9) versions a collection supports.
While there is a runtime warning when using a collection with an ansible-core version it does not support, it would prevent a lot of unnecessary issues if ansible-galaxy collection install would - like any other good package manager - only install collections for an ansible-core version that are actually supported.
This is annoying for a user since when installing a collection on an older ansible-core version, you can easily install a collection that will not work with your ansible-core version.
This is also very annoying for collection maintainers and developers since right now, dropping support for an ansible-core version is a breaking change. If the package manager (ansible-galaxy) would consider requires_ansible, one could start dropping support for ansible-core versions in minor releases according to semantic versioning.