From a8003fe7323cc10b9b74a4ef3bc4f0f02a51aa5e Mon Sep 17 00:00:00 2001 From: Sloane Hertel <19572925+s-hertel@users.noreply.github.com> Date: Mon, 9 Mar 2026 16:58:00 -0400 Subject: [PATCH] Clarify ansible-galaxy changelog fragment (#86626) Co-authored-by: Don Naro --- .../install-ansible-core-compatible-collections.yml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/changelogs/fragments/install-ansible-core-compatible-collections.yml b/changelogs/fragments/install-ansible-core-compatible-collections.yml index 4e24005d415..24f6d86c742 100644 --- a/changelogs/fragments/install-ansible-core-compatible-collections.yml +++ b/changelogs/fragments/install-ansible-core-compatible-collections.yml @@ -1,6 +1,5 @@ -bugfixes: +major_changes: - >- - ``ansible-galaxy install`` and ``ansible-galaxy collection install|download`` - now consider - the ``COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH`` configuration. - Collections which will cause a warning/error at load time are no longer installed/downloaded. + ``ansible-galaxy install`` and ``ansible-galaxy collection install|download`` - + collections that declare a ``requires_ansible`` version that is not compatible with the running ansible-core version are now excluded from installation and download by default. In previous versions, ansible-galaxy would install such collections even if doing so resulted in an error at load time. To restore the previous behavior, set ``COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH`` to ``ignore`` in your configuration. (https://github.com/ansible/ansible/issues/78539)