# Release announcement : Ansible Community Package 7.6.0

**URL:** <https://forum.ansible.com/t/release-announcement-ansible-community-package-7-6-0/38020>\
**Category:** Ansible Project\
**Created:** [May 23, 2023, 12:15pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-7-6-0/38020 "2023-05-23T12:15:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anwesha\_Das](https://avatars.discourse-cdn.com/v4/letter/a/3be4f8/32.png) [@Anwesha\_Das](https://forum.ansible.com/u/Anwesha_Das)\
**Post date:** [May 23, 2023, 12:15pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-7-6-0/38020/1 "2023-05-23T12:15:23Z")

</div>

Hello everyone,

We're happy to announce the release of the Ansible 7.6.0 package!

Ansible 7.6.0 includes ansible-core 2.14.6 as well as a curated set of  
Ansible collections that provide a vast number of modules and plugins.

How to get it

---

<div class="post-metadata">

**Author:** ![Nico\_Kadel-Garcia](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nico_kadel-garcia/32/9998_2.png) [@Nico\_Kadel-Garcia](https://forum.ansible.com/u/Nico_Kadel-Garcia)\
**Post date:** [May 26, 2023, 12:07pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-7-6-0/38020/2 "2023-05-26T12:07:08Z")

</div>

> Hello everyone,
> 
> We're happy to announce the release of the Ansible 7.6.0 package!
> 
> Ansible 7.6.0 includes ansible-core 2.14.6 as well as a curated set of  
> Ansible collections that provide a vast number of modules and plugins.

Please, stop saying this. This line of the documentation is simply not  
true. "ansible-core" is s distinct code base, from a different repo,  
published as a different tarball. The ansible tarball is \*only\* a  
curated set of ansible collections. It's huge, and awkward to manage,  
and it does not contain the actually critical ansible-core3 that all  
ansible software users require.

The ansible tarball is \*locked\* to specific releases of ansible-core  
by the "ansible.egg-info/requires.txt" file, which currently lists:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ansible-core~=2.14.6

Having a listed dependency is far from "including" a distinct code  
base. Please use the correct verb. To describe it better, may I  
suggest:

&nbsp;&nbsp;&nbsp;&nbsp;\> Ansible 7.6.0 requires and if not found, attempts to  
automatically install ansible-core 2.14.6 The Ansible package provides  
a large, curated set of Ansible collection published modules and  
plugins.

---

<div class="post-metadata">

**Author:** ![Nico\_Kadel-Garcia](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nico_kadel-garcia/32/9998_2.png) [@Nico\_Kadel-Garcia](https://forum.ansible.com/u/Nico_Kadel-Garcia)\
**Post date:** [May 26, 2023, 12:08pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-7-6-0/38020/3 "2023-05-26T12:08:54Z")

</div>

> \>  
> \> Hello everyone,  
> \>  
> \> We're happy to announce the release of the Ansible 7.6.0 package!  
> \>  
> \> Ansible 7.6.0 includes ansible-core 2.14.6 as well as a curated set of  
> \> Ansible collections that provide a vast number of modules and plugins.
> 
> Please, stop saying this. This line of the documentation is simply not  
> true. "ansible-core" is s distinct code base, from a different repo,  
> published as a different tarball. The ansible tarball is \*only\* a  
> curated set of ansible collections. It's huge, and awkward to manage,  
> and it does not contain the actually critical ansible-core3 that all  
> ansible software users require.

Argh. I typed "ansible-core3" rather than "ansible-core". Forgive me,  
the cat wanted his breakfast. He's fed now!