Release announcement: Ansible community package 11.0.0rc1 (Pre-Release)

News & Announcements Ecosystem Releases
, , ,
1

Hello everyone,

We’re happy to announce the release of the Ansible 11.0.0rc1 package pre-release!

Ansible 11.0.0rc1 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.0rc1 --user

The sources for this release can be found here:

Release tarball:

https://files.pythonhosted.org/packages/27/6a/988a7a93a1616e6dd08b0df9d97fcbbd85f3d32e1dd38159a9259b737717/ansible-11.0.0rc1.tar.gz

SHA256:

ddefbe786059d943109f1669a01011ebea2458fd3628d4badbe75de76f4bf9fc

Wheel package:

https://files.pythonhosted.org/packages/2e/33/5a5da7e5cf01b0619f81789ce659911373a90dd37d8b8e09a0bfffd7d399/ansible-11.0.0rc1-py3-none-any.whl

SHA256:

88739b7a36be6c4dc33949cf322ad79c96872e649b1576cb440c211044c848d7

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 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.0rc1?

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:

https://forum.ansible.com

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

1 Like