Skip to content

[WIP] Collection requirements: declare that Galaxy artifacts must not be deleted once they appear in Ansible releases #2678

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: devel
Choose a base branch
from

Conversation

felixfontein
Copy link
Collaborator

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).

@ansible-documentation-bot ansible-documentation-bot bot added the sc_approval This PR requires approval from the Ansible Community Steering Committee label Jun 3, 2025
@bcoca
Copy link
Member

bcoca commented Jun 3, 2025

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.

@felixfontein
Copy link
Collaborator Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sc_approval This PR requires approval from the Ansible Community Steering Committee
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants