Hi all,

We're happy to announce that the Ansible 5.8.0 package has been released !

Ansible 5.8.0 includes ansible-core 2.12 as well as a curated set of
Ansible collections to provide a vast number of modules and plugins.

This is a major version update from Ansible 4.x which included
ansible-core 2.11 and there may be backwards incompatibilities in the
core playbook language.

Please see the porting guide (linked at the bottom) for details.

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 5:

```
$ pip uninstall ansible ansible-base
$ pip install ansible==5.8.0 --user
```

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

Ansible 5.8.0: 
https://pypi.python.org/packages/source/a/ansible/ansible-5.8.0.tar.gz
SHA256: fa056476201f40625fb36d95c5041ef463880be18be5c73b998b57b401967863

What's new in Ansible 5.8.0
---------------------------

* The changelog for ansible-core 2.12 installed by this release of
ansible is available here:
https://github.com/ansible/ansible/blob/stable-2.12/changelogs/CHANGELOG-v2.12.rst

* Collections which have opted into being a part of the Ansible-5
unified changelog will have an entry on this page:
https://github.com/ansible-community/ansible-build-data/blob/main/5/CHANGELOG-v5.rst

* For collections which have not opted into the unified changelog, you
may find more information on https://galaxy.ansible.com or their
source repository.
For example, the community.crypto collection would be found at
https://galaxy.ansible.com/community/crypto and you can find a link to
the source repository under the "Repo" button at the top right.

What's the schedule for new Ansible releases after 5.8.0 ?
---------------------------------------------------------

* Maintenance releases of Ansible 5.x will occur approximately every
three weeks until the release of Ansible 6.0.0. They will contain bugfixes
and new features but no backwards incompatibilities.

* Ansible 6.0.0 (which will include ansible-core 2.13) is expected to
be released around 2022-06-21.
More information can be found in the roadmap:
https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_6.html

* Please note that the release of ansible-core 2.13 in May 2022 will
coincide with the end-of-life of ansible 2.9 and ansible-base 2.10:
https://groups.google.com/g/ansible-announce/c/kegIH5_okmg/

* Except for ansible-2.9.x, older versions of ansible are no longer
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:
https://github.com/ansible/community/tree/main/meetings#wednesday

Porting Help
-------------

A unified porting guide for collections which have opted-in is available here:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_5.html

Getting collection updates from Ansible 5 with ansible-core 2.11.x
-----------------------------------------------------------------

Ansible 5 includes ansible-core 2.12.x which has raised the minimum
python requirement to python>=3.8 and users have expressed an interest
in getting collection updates as they ship in Ansible 5 while keeping
ansible-core 2.11.x which still supports python>=2.7.
An ansible-galaxy requirements file based on the collections from
Ansible 5 has been made available for this use case:
https://github.com/ansible-community/ansible-build-data/blob/main/5/galaxy-requirements.yaml

Once the requirements file has been downloaded, the collections can be
installed by running:
"ansible-galaxy collection install -r galaxy-requirements.yaml"

On behalf of the Ansible community, thank you and happy automating !

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-devel/CAH7C%2BPoN-%2BJJ0SCSL1BfR7pCFS_U32z3RBquO%3D1xGHn3KdNOPA%40mail.gmail.com.

Reply via email to