# Version of collections included in Ansible distro?

**URL:** <https://forum.ansible.com/t/version-of-collections-included-in-ansible-distro/35343>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [June 14, 2021, 7:58am UTC](https://forum.ansible.com/t/version-of-collections-included-in-ansible-distro/35343 "2021-06-14T07:58:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Erik\_Godding\_Boye](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@Erik\_Godding\_Boye](https://forum.ansible.com/u/Erik_Godding_Boye)\
**Post date:** [June 14, 2021, 7:58am UTC](https://forum.ansible.com/t/version-of-collections-included-in-ansible-distro/35343/1 "2021-06-14T07:58:49Z")

</div>

Greetings,

I am trying to understand how (and when) the versions of collections included in the Ansible distro are decided?

We are building our own container image for ansible stuff, and the image is rebuilt nightly. After hitting a bug with the recent ansible 4.1.0 release, we submitted [this issue](https://github.com/ansible-collections/community.crypto/issues/247) to the community.crypto collection. The bug was fixed extremely fast on Friday, and version 1.7.1 of the collection was released. But still, our image is not updated today?

Our image is installing ansible from PyPi:  
python -m pip install -q --no-cache-dir ansible~=${ANSIBLE\_VERSION}

I can of course force-install the latest version of the collection into the image (ansible-galaxy collection install community.crypto), but I was expecting bug fixes/patches to be applied by the ansible distro - probably by some included requirements-file.

Any input that can help me understand this would be greatly appreciated!

Regards,  
Erik

---

<div class="post-metadata">

**Author:** ![Akasurde](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akasurde/32/230_2.png) [@Akasurde](https://forum.ansible.com/u/Akasurde)\
**Post date:** [June 14, 2021, 8:02am UTC](https://forum.ansible.com/t/version-of-collections-included-in-ansible-distro/35343/2 "2021-06-14T08:02:56Z")

</div>

You might want to check this repo - [https://github.com/ansible-community/ansible-build-data](https://github.com/ansible-community/ansible-build-data)

This repo contains version information in which Ansible Community versions are built.

---

<div class="post-metadata">

**Author:** ![Erik\_Godding\_Boye](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@Erik\_Godding\_Boye](https://forum.ansible.com/u/Erik_Godding_Boye)\
**Post date:** [June 14, 2021, 8:11am UTC](https://forum.ansible.com/t/version-of-collections-included-in-ansible-distro/35343/3 "2021-06-14T08:11:05Z")

</div>

Thanks Abhijeet,

So this means we’ll have to wait for an eventual 4.1.1 release of ansible or 4.2.0, right?

Erik

mandag 14. juni 2021 kl. 10:03:26 UTC+2 skrev Abhijeet Kasurde:

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [June 14, 2021, 8:14am UTC](https://forum.ansible.com/t/version-of-collections-included-in-ansible-distro/35343/4 "2021-06-14T08:14:28Z")

</div>

Hi Erik,

> So this means we'll have to wait for an eventual 4.1.1 release of  
> ansible or 4.2.0, right?

yes, you will (unfortunately) have to wait for 4.2.0, which will be  
released in ~2 weeks.

Best,  
Felix

---

<div class="post-metadata">

**Author:** ![Erik\_Godding\_Boye](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@Erik\_Godding\_Boye](https://forum.ansible.com/u/Erik_Godding_Boye)\
**Post date:** [June 14, 2021, 8:19am UTC](https://forum.ansible.com/t/version-of-collections-included-in-ansible-distro/35343/5 "2021-06-14T08:19:38Z")

</div>

Thanks for clearifying this Abhijeet and Felix. We are applying the workaround for now, so no problem. 🙂 I just wanted to understand how this works, and now I do!

Erik

mandag 14. juni 2021 kl. 10:14:44 UTC+2 skrev Felix Fontein: