# Release announcement: Ansible Community Package 8.6.1 **URL:** \ **Category:** Ecosystem Releases\ **Tags:** community, news, release, distro-packaging, galaxy-ng\ **Created:** [November 7, 2023, 7:21pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-8-6-1/2217 "2023-11-07T19:21:39Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![oranod](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/oranod/32/1434_2.png) [@oranod](https://forum.ansible.com/u/oranod)\ **Post date:** [November 7, 2023, 7:21pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-8-6-1/2217/1 "2023-11-07T19:21:40Z")
Hello everyone, We’re happy to announce the release of the Ansible 8.6.0 package! Ansible 8.6.0 includes ansible-core 2.15.6 as well as a curated set of Ansible collections that provide a vast number of modules and plugins. ## How to get it This release is available on PyPI and can be installed with pip: `$ python3 -m pip install ansible==8.6.0 --user` The sources for this release can be found here: Release tarball: [https://files.pythonhosted.org/packages/50/d4/97b8f6d10c6881c161d8677850062c9d8d4838ef8a491f34779c12253278/ansible-8.6.0.tar.gz](https://files.pythonhosted.org/packages/50/d4/97b8f6d10c6881c161d8677850062c9d8d4838ef8a491f34779c12253278/ansible-8.6.0.tar.gz) SHA256: 95f4e593274d59d53f36f62207535b7d272adc2701ac7a0ed7af6a6d81637a60 Wheel package: [https://files.pythonhosted.org/packages/74/ef/54a04b6abbeeb88689bbb13eb66304733e98dc433a1ec6106d01b1492f67/ansible-8.6.0-py3-none-any.whl](https://files.pythonhosted.org/packages/74/ef/54a04b6abbeeb88689bbb13eb66304733e98dc433a1ec6106d01b1492f67/ansible-8.6.0-py3-none-any.whl) SHA256: 6adf5a8f3f13127c2a1e3554d484aac169c41427507f73f9b6340864cada37ea ## Some important details Python wheels are now available for both Ansible 8 and ansible-core 2.15 resulting in significantly improved installation performance. In addition, Ansible 8 does not install some unnecessary files from the included Ansible collections such as tests or hidden files and directories. This further improves installation performance and reduces the size on disk. These files are still available in the source tarball if needed. Collections which have opted-in to being a part of the Ansible 8 unified changelog will have an entry on this page: > For collections which have not opted-in to the unified changelog, you may find more information on > **[Collection Index — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/latest/collections/)** source repository. For example, the community.crypto collection is available at > **[Community.Crypto — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/latest/collections/community/crypto/index.html)** and you can find a link to the source repository under the “Repository(Sources)” button. The changelog for ansible-core 2.15.6 installed by this release of Ansible 8 can be found here: > ## What’s the schedule for new Ansible releases after 8.6.0? The next release roadmap can be found at > **[Ansible Roadmap — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/devel/roadmap/ansible_roadmap_index.html)** Subscribe to the Bullhorn for all future release dates, announcements, and Ansible contributor community news. Visit this link to subscribe: [https://bit.ly/subscribe-bullhorn](https://bit.ly/subscribe-bullhorn) You can find all past Bullhorn issues on the official wiki page: [https://github.com/ansible/community/wiki/News#the-bullhorn](https://github.com/ansible/community/wiki/News#the-bullhorn) Join the new Ansible Community Forum to follow along and participate in all the project and release related discussions and announcements. Feel free to share your thoughts, feedback, ideas and concerns there. Register here to join the Ansible Forum: [http://forum.ansible.com](http://forum.ansible.com) ## Porting Help A unified porting guide for collections that have opted-in is available here: > **[Ansible 8 Porting Guide — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/devel/porting_guides/porting_guide_8.html)** ## Getting collection updates from Ansible 8 with older releases of ansible-core Ansible 8 includes ansible-core 2.15 Based on your requirements, you can get collection updates as they ship in the Ansible “batteries included” package while continuing to use older versions of ansible-core. An ansible-galaxy requirements file based on the collections from Ansible 8 has been made available for this use case: > After you download the requirements file, the collections can be installed by running this command: “ansible-galaxy collection install -r galaxy-requirements.yaml” ## Special Thanks We would like to give a shoutout with a big THANK YOU to @gotmax23 for making this release happen! On behalf of the Ansible community, thank you and happy automating! Cheers Ansible Community Team ---
**Author:** ![oranod](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/oranod/32/1434_2.png) [@oranod](https://forum.ansible.com/u/oranod)\ **Post date:** [November 10, 2023, 4:28pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-8-6-1/2217/2 "2023-11-10T16:28:20Z")
Heads up that we’ve released a hotfix with the Ansible 8.6.1 package! ## How to get it This release is available on PyPI and can be installed with pip: `$ python3 -m pip install ansible==8.6.1 --user` The sources for this release can be found here: Release tarball: [https://files.pythonhosted.org/packages/f9/41/714d5a1e4d46e522df144b6745fa2002760114fd586eea8538b6e42be26c/ansible-8.6.1.tar.gz](https://files.pythonhosted.org/packages/f9/41/714d5a1e4d46e522df144b6745fa2002760114fd586eea8538b6e42be26c/ansible-8.6.1.tar.gz) SHA256: 18b397580c1f05ce5de1fe238508dd81218d278667956d2f7709320176c3ed4a Wheel package: [https://files.pythonhosted.org/packages/b3/b1/9b9f975f491fedb5562e5eba17a1b6adab86f408e1168b59f5633bd36801/ansible-8.6.1-py3-none-any.whl](https://files.pythonhosted.org/packages/b3/b1/9b9f975f491fedb5562e5eba17a1b6adab86f408e1168b59f5633bd36801/ansible-8.6.1-py3-none-any.whl) SHA256: 222735c32d2d2749f207e55ef740638bb97c7aaaa8b63bb7c7592d447da47584 ---
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [November 26, 2023, 7:54pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-8-6-1/2217/3 "2023-11-26T19:54:10Z")
Hi @oranod I see you have _refurbished_ the 8.6.0 announcement post for the 8.6.1 release. May I suggest we refrain from doing that in the future because it may be confusing, especially for new users? there are still a number of references to the 8.6.0 version throughout the topic. Right now I am writing a post about Ansible in the internal blog of the company, and I am referring to this topic as 8.6.1, but I am fully expecting people to come back and point me that _it says `pip install ansible==8.6.0` right there!!!_ Anyways, just my $0.02 on this. ---
**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:** [November 26, 2023, 9:37pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-8-6-1/2217/4 "2023-11-26T21:37:45Z")
I agree it’s better to create a separate topic for the new release instead, and add a comment to the previous one pointing to the new one. Updating the topic with an appendum like `[SUPERSEDED BY 8.6.1]` is OK from my point of view, but replacing it (as in this case) makes this pretty confusing. ---
**Author:** ![oranod](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/oranod/32/1434_2.png) [@oranod](https://forum.ansible.com/u/oranod)\ **Post date:** [November 28, 2023, 4:02pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-8-6-1/2217/5 "2023-11-28T16:02:33Z")
@russoz and @felixfontein Hey, just back from a trip so maybe a bit delayed in responding. Apologies for the confusion caused with the hotfix announcement. I’ll bring this to the team to make sure we don’t repeat the same mistake and do better next time. Thanks for the feedback! ---
**Author:** ![cybette](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/cybette/32/16_2.png) [@cybette](https://forum.ansible.com/u/cybette)\ **Post date:** [November 29, 2023, 12:29pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-8-6-1/2217/6 "2023-11-29T12:29:39Z")
Thanks for the good points raised against reusing the annoucement @russoz and @felixfontein! We didn’t think things through enough when announcing the hotfix, the onus is on me as well. We’ll know better next time! ---
**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\ **Post date:** [November 29, 2023, 2:49pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-8-6-1/2217/7 "2023-11-29T14:49:47Z")
I agree a separate topic for each release makes sense (including hotfixes). That way anyone who is ‘watching first post’ for announcements will still get it. I don’t know if anyone gets an email for an edited topic? ---
**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\ **Post date:** [November 29, 2023, 4:42pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-8-6-1/2217/8 "2023-11-29T16:42:19Z")
> [@samccann](#): > > I don’t know if anyone gets an email for an edited topic? As far as I know, they don’t. Authors get a 10min grace period for typo edits etc. before the emails go out, but after that, they’re sent, that’s it.