Collection requirements: declare that Galaxy artifacts must not be deleted once they appear in Ansible releases #2678
Conversation
… Ansible releases.
ansible-documentation-bot
bot
added
the
sc_approval
|
I would go a step further and mention you cannot delete versions of a collection that would break the build: for example, you require my.coll >= 2.0, deleting everything except 1.9 version would still break the build. |
|
@bcoca this is implicitly handled for collections included in Ansible, since all dependencies also have to be part of it, hence these might also not be deleted. For general collections the situation is different, but these aren't covered by these requirements anyway. |
felixfontein
changed the title
felixfontein
added
backport-2.18
|
Approved according to https://forum.ansible.com/t/43132/13. |
Backport to stable-2.18: 💚 backport PR created✅ Backport PR branch: Backported as #2722 🤖 @patchback |
|
@bcoca @gotmax23 @mariolenz thanks! |
Backport to stable-2.19: 💚 backport PR created✅ Backport PR branch: Backported as #2723 🤖 @patchback |
… Ansible releases. (#2678) (#2722) (cherry picked from commit a514f0c) Co-authored-by: Felix Fontein <[email protected]>
… Ansible releases. (#2678) (#2723) (cherry picked from commit a514f0c) Co-authored-by: Felix Fontein <[email protected]>
This updates the Ansible community package collections requirements. This change was prompted by the deletion of a collection release already contained in Ansible 12.0.0b4, which broke the build of that release, and also of all newer and upcoming Ansible 12 releases (as the changelog can no longer be built).