Ansible 4.2.0 released

Skip to first unread message

Toshio Kuratomi

Jun 30, 2021, 11:43:48 AM6/30/21
to ansible-devel,,
Hi all,

We're happy to announce that the ansible-4.2.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.

How to get it

Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need to uninstall Ansible and Ansible Base before
installing Ansible 4:

$ pip uninstall ansible ansible-base
$ pip install ansible==4.2.0 --user

The tar.gz of the release can be found here:

* Ansible 4.2.0
* SHA256: 737d819ffbd7a80c28795b4edd93e59ad21e6e6d53af0d19f57412814f9260d0

What's new in Ansible 4.2.0

* We've added a way to get the version of the Ansible package that is
installed programmatically:

$ python -c 'from ansible_collections.ansible_release import
ansible_version; print(ansible_version)'

* Collections which have opted into being a part of the Ansible-4
unified changelog will have an entry on this page:

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on for information about their

* You can find more information for those on For instance, the community.crypto
collection listed in the ansible-4.2.0.deps file has a galaxy page at

* Changelog for ansible-core-2.11.2 which this release of ansible

What's the schedule for new Ansible releases after 4.2.0?

* Except for ansible-2.9.x, older versions of ansible are not seeing
maintenance releases. If there is a desire for maintenance releases
of older versions, drop by a Community Working Group Meeting to
discuss how you can help. ( )

* Maintenance releases of ansible-4.x will occur roughly every three
weeks. Expect 4.3.0 roughly on July 20.

* We're planning to release Ansible-5.0.0 in November, 2021.

Porting Help

There's a unified porting guide for collections which have opted-in.
You can find that at:


Reply all
Reply to author
0 new messages