Skip to content
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

Add community.okd, a collection which was broken out of the community.general collection, for 2.10.4 #39

Merged
merged 1 commit into from Dec 1, 2020

Conversation

abadger
Copy link
Contributor

@abadger abadger commented Dec 1, 2020

These are the changes needed to add a new collection to a stable release. In this PR we add community.okd which was spun out of community.general and thus is allowed into 2.10.x according to the policies approved at the community irc meeting.

I had to do this manually (add the collection name to ansible.in and look on galaxy.ansible.com for the current version and add the collection with the appropriate version range to the ansible-2.10.build file.) I've opened a ticket on the antsibull repo to add code to do that at some point in the future.

@abadger abadger merged commit f962068 into main Dec 1, 2020
@abadger abadger deleted the 2.10-new-collections branch December 1, 2020 09:41
@felixfontein
Copy link
Contributor

@abadger does the version range also needs to be added for the other collections we added to ansible.in last(?) week?

@abadger
Copy link
Contributor Author

abadger commented Dec 1, 2020

Yes, it does. I'm opening a PR for that now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants