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

- ansible-core 2.13.6


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

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

The release artifacts can be found here:

* ansible-core 2.13.6
    Wheel:
https://files.pythonhosted.org/packages/8d/15/fb1db37ad9583724c6f378f7c9d77da3a56c5ebe0f8c470947c078b4e2f2/ansible_core-2.13.6-py3-none-any.whl
    Source:
https://files.pythonhosted.org/packages/27/82/d3f91d2bff791291c6fa5eddd0a338546ca4a63d5c4bf80ca1f44f6a438d/ansible-core-2.13.6.tar.gz


Checksums
---------

# ansible_core-2.13.6-py3-none-any.whl: 2076597 bytes
SHA256 (ansible_core-2.13.6-py3-none-any.whl) =
e31fd550a5ea9423f1fc1391de6b41bb0d264a83bbfc9c7edfef0f78b7624fd3
# ansible-core-2.13.6.tar.gz: 13938462 bytes
SHA256 (ansible-core-2.13.6.tar.gz) =
31fe322b63290674a8f7386110df501f0044aa44890be3ab313a6e225b9a29cf


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

This release is a maintenance release containing numerous bugfixes.

The full changelog can be found here:

* ansible-core 2.13.6

https://github.com/ansible/ansible/blob/v2.13.6/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 28
November 2022. 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/CAD8N0v8xgFxBGkx7Z8MEa_iCySoXLqpeH%3DRWcbEmjDZ1Se3AcQ%40mail.gmail.com.

Reply via email to