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

- ansible-core 2.13.7


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

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

The release artifacts can be found here:

* ansible-core 2.13.7
    Wheel:
https://files.pythonhosted.org/packages/4f/f6/c4365655d62f6688b52e250316ffbd6beabeccdcd91d08d51bf9066c8dd6/ansible_core-2.13.7-py3-none-any.whl
    Source:
https://files.pythonhosted.org/packages/68/c9/ddab83ed69c3ce120af4f064bc56976442e4d1d595a787131e4b14cf6468/ansible-core-2.13.7.tar.gz


Checksums
---------

# ansible_core-2.13.7-py3-none-any.whl: 2076604 bytes
SHA256 (ansible_core-2.13.7-py3-none-any.whl) =
6005c24e45ff59497a7fe24411825fcba862585bc6bde83d6d48242c97042aba
# ansible-core-2.13.7.tar.gz: 13940230 bytes
SHA256 (ansible-core-2.13.7.tar.gz) =
a9d5f942ff0dcbeec3d7183a898ea4f656d233d6055d4bc8e22e37b013b1881a


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

This release is a maintenance release containing numerous bugfixes.

The full changelog can be found here:

* ansible-core 2.13.7

https://github.com/ansible/ansible/blob/v2.13.7/changelogs/CHANGELOG-v2.13.rst


What's the schedule for future maintenance releases?
----------------------------------------------------

The next batch of release candidates is planned to be released on 23 January
 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!
-- 
Matt Martz
@sivel
sivel.net

-- 
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/CAD8N0v_M0WQKwHQG%3Df_7jYnAJyjG09sHc%2BREwVLwKy0E7ftwHA%40mail.gmail.com.

Reply via email to