Hi all- we're happy to announce the general release of:

ansible-core 2.16.1


How to get it
-------------

$ python3 -m pip install --user ansible-core==2.16.1

The release artifacts can be found here:

# Built Distribution: 2249752 bytes
# SHA256: 8fc972ba6ba2161ecbde8166c0042080726c754f69ecb3ccd8c6636c98dc1c7e
https://files.pythonhosted.org/packages/f9/31/585576f619a974d9cdef009251d056a00e240c546f222d4bdb192d9e9208/ansible_core-2.16.1-py3-none-any.whl
# Source Distribution: 3162449 bytes
# SHA256: 4fd1b3c86237507c67113f6770d2470f87477cd88244938d100a2d0fc37bf986
https://files.pythonhosted.org/packages/6f/3f/1dc35ba302137a4b00d17a42a47859c9e133ea2af56a285418e6c22be05d/ansible-core-2.16.1.tar.gz


What's new
----------

This release includes a fix for CVE-2023-5764, where internal templating
actions could result in unsafe data losing its unsafe designation.

The devel branch is still currently vulnerable to CVE-2023-5764 and will be
mitigated with a different fix in the coming weeks. Production users should
ensure they are using released stable versions.

The full changelog can be found here:

https://github.com/ansible/ansible/blob/v2.16.1/changelogs/CHANGELOG-v2.16.rst


Schedule for future releases
----------------------------

The next release candidate is planned to be released on 25 December 2023.
The next general availability release will be one week after.


Porting help
------------

If you discover any errors or if any of your working playbooks break when
you upgrade, please use the following link to report the regression:

https://github.com/ansible/ansible/issues/new/choose

In your issue, be sure to mention the version that works and the one that
doesn't.

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAD8N0v8FxVNQ%2BGaf-_QC9xasS2N1tzsXKQ5LNMtFBEkDUgYb6Q%40mail.gmail.com.

Reply via email to