ansible/changelogs
Patrick Kingston 1e31c7c819
Fix ansible-galaxy collection metadata/file system location discrepancy (#86402)
* Fix discrepancy between ansible-galaxy and ansible runtime when identifying usable collections

When enumerating usable collections, ansible-galaxy validates the galaxy metadata in the MANIFEST.json/galaxy.yml matches the collection path.

When the metadata is incorrect ansible-galaxy emits a warning and falls back to using no metadata since it is not required for usable collections.

* ansible-galaxy collection verify now evaluates the collection that will be used at runtime, even if a collection inaccurately documents the same namespace and name earlier in the search path

* Add integration tests for ansible-galaxy collection verify, list, and install
2026-02-02 17:17:36 -05:00
..
fragments Fix ansible-galaxy collection metadata/file system location discrepancy (#86402) 2026-02-02 17:17:36 -05:00
changelog.yaml Bump devel to 2.21 (#85992) 2025-10-14 15:35:21 -05:00
config.yaml [changelog config] Ansible Base -> ansible-core (#73739) 2021-02-27 21:51:11 -06:00
README.md Convert non-docs *.rst files to *.md (#81217) 2023-07-11 11:42:40 -07:00

Changelogs

As part of the release process a version-specific CHANGELOG-vX.Y.rst will be generated from fragments in the fragments directory.

On release branches once a release has been created, consult the branch's version-specific file for changes that have occurred in that branch. The devel branch does not have a generated changelog, only changelog fragments.