Hello everyone,
We’re happy to announce the release of the Ansible 11.0.0b2 package pre-release!
Ansible 11.0.0b2 depends on ansible-core 2.18.0 and includes a curated set of Ansible collections that provide a vast number of modules, plugins, and roles. This is a pre-release of Ansible 11.
How to get it
This pre-release is available on PyPI and can be installed with pip:
python3 -m pip install ansible==11.0.0b2 --user
The sources for this release can be found here:
Release tarball:
SHA256:
bb805e37e9b6150e62a925009240c6b3eec72d5de5f238db3a2e90ee1064da0c
Wheel package:
SHA256:
04f8b9fda72537161a1802df92d760530fa0813255404e8ccfda9bf6729f450c
Some important details
Ansible 11.0.0b2 was released to re-add netapp.storagegrid, which was erroneously not re-added to 11.0.0b1 (see [Vote ended on 2024-11-05] Unmaintained collection: netapp.storagegrid - #30 by felixfontein for details). This is the only change since 11.0.0b1. We plan to continue with 11.0.0rc1 beginning of next week, as originally scheduled.
ansible-core is a separate package on which ansible depends. pip install ansible installs ansible-core, but it can also be installed independently of the ansible package.
Collections that have opted to join the Ansible 11 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
https://docs.ansible.com/ansible/latest/collections
or on the collection source repository. For example, the community.crypto collection is available at
https://docs.ansible.com/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.18 installed by this release of Ansible 11 can be found here:
What’s the schedule for new Ansible releases after 11.0.0b2?
The next release roadmap can be found at
https://docs.ansible.com/ansible/devel/roadmap/ansible_roadmap_index.html
The Ansible community package release schedule follows the Ansible Core release schedule, including, for example, delays for holidays. This means Ansible releases happen every four weeks through most of the year, but release dates may be delayed when Ansible Core releases are.
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
You can find all past Bullhorn issues on the Ansible Community Forum at:
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:
Porting Help
A unified porting guide for collections that have opted in is available here:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_11.html
Getting collection updates from Ansible 11 with older releases of ansible-core
Ansible 11 depends on ansible-core 2.18. Depending on your needs, you can get collection updates as they ship in the Ansible “batteries included” package while continuing to use older versions of ansible-core.
See the ansible-galaxy requirements file based on the collections from Ansible 11 for this use case:
After you download the requirements file, you can install the collections by running the following command:
ansible-galaxy collection install -r galaxy-requirements.yaml
On behalf of the Ansible community, thank you and happy automating!
Cheers,
Ansible Release Management Working Group