Hello everyone,
We’re happy to announce the release of the Ansible 12.0.0b3 package pre-release!
Ansible 12.0.0b3 depends on ansible-core 2.19.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 12.
Please note that Ansible 12.0.0 is delayed due to important parts of ansible.netcommon and several network connections not working with ansible-core 2.19 right now. For that reason, we decided to keep publishing beta releases until ansible.netcommon is fixed, and stopped feature freeze until then to avoid other collections becoming stale. Also Ansible 12.0.0 will depend on ansible-core 2.19.1 (or whichever version is released by then), instead of ansible-core 2.19.0. See this forum thread for more information.
How to get it
This pre-release is available on PyPI and can be installed with pip:
python3 -m pip install ansible==12.0.0b3 --user
The sources for this release can be found here:
Release tarball:
SHA256:
4edb0964d4aa7a4752331d63a70224d2975769f55018f33e5f6d1bd9ef59d4da
Wheel package:
SHA256:
a677bcd0c443d01177967766fc5d832c65989d4f444db2eb059abd2eafd93053
Some important details
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 12 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
or on the collection source repository. For example, the community.crypto collection is available at
and you can find a link to the source repository under the “Repository (Sources)” button.
The changelog for ansible-core 2.19 installed by this release of Ansible 12 can be found here:
What’s the schedule for new Ansible releases after 12.0.0b3?
The next release roadmap can be found at
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:
Getting collection updates from Ansible 12 with older releases of ansible-core
Ansible 12 depends on ansible-core 2.19. 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 12 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