# Release announcement: Ansible community package 11.13.0 **URL:** \ **Category:** Ecosystem Releases\ **Tags:** release-management, distro-packaging, release, galaxy-ng\ **Created:** [December 9, 2025, 9:03pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-11-13-0/44979 "2025-12-09T21:03:02Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [December 9, 2025, 9:03pm UTC](https://forum.ansible.com/t/release-announcement-ansible-community-package-11-13-0/44979/1 "2025-12-09T21:03:02Z")
Hello everyone, We’re happy to announce the release of the Ansible 11.13.0 package! **This is the final 11.X.X release.** Ansible 11.13.0 depends on ansible-core 2.18.12 and includes a curated set of Ansible collections that provide a vast number of modules, plugins, and roles. ## How to get it This release is available on PyPI and can be installed with pip: ```console python3 -m pip install ansible==11.13.0 --user ``` The sources for this release can be found here: Release tarball: [https://files.pythonhosted.org/packages/08/26/182bfd55a1d5a24148e52589decba98a0c6fe3c9b15db19df342a6b4f072/ansible-11.13.0.tar.gz](https://files.pythonhosted.org/packages/08/26/182bfd55a1d5a24148e52589decba98a0c6fe3c9b15db19df342a6b4f072/ansible-11.13.0.tar.gz) SHA256: `c15a046c851c22e8430783bdbcb8f6603c35f0d7c766992ca0a6a9ed975e4a9a` Wheel package: [https://files.pythonhosted.org/packages/13/03/ccb0340249d5a3f2607b384e8fa11b5ce7ab7812da14bb4157b9e1a51be1/ansible-11.13.0-py3-none-any.whl](https://files.pythonhosted.org/packages/13/03/ccb0340249d5a3f2607b384e8fa11b5ce7ab7812da14bb4157b9e1a51be1/ansible-11.13.0-py3-none-any.whl) SHA256: `7f1c9c6a6026ff214d9240647e4d2b019b2a9d4c7a2bc733932bcf92af80ab04` ## Some important details ansible-core is a separate package on which ansible depends. `pip install ansible` installs `ansible-core`, but it can also be installed independently of the ansible package. Collections that have opted to join the Ansible 11 unified changelog will have an entry on this page: [https://github.com/ansible-community/ansible-build-data/blob/11.13.0/11/CHANGELOG-v11.md](https://github.com/ansible-community/ansible-build-data/blob/11.13.0/11/CHANGELOG-v11.md) For collections which have not opted-in to the unified changelog, you may find more information on [Collection Index — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/latest/collections) or on the collection source repository. For example, the community.crypto collection is available at [Community.Crypto — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/latest/collections/community/crypto/index.html) and you can find a link to the source repository under the “Repository (Sources)” button. The changelog for ansible-core 2.18 installed by this release of Ansible 11 can be found here: [ansible/changelogs/CHANGELOG-v2.18.rst at v2.18.12 · ansible/ansible · GitHub](https://github.com/ansible/ansible/blob/v2.18.12/changelogs/CHANGELOG-v2.18.rst) ## What’s the schedule for new Ansible releases after 11.13.0? This is the last release of Ansible version 11. Ansible 11.X.X will not receive any additional features, bugfixes, or security fixes. From now on, only Ansible 12.X.X will receive updates. The next release roadmap can be found at [Ansible Roadmap — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/devel/roadmap/ansible_roadmap_index.html) The Ansible community package release schedule follows the Ansible Core release schedule, including, for example, delays for holidays. This means Ansible releases happen every four weeks through most of the year, but release dates may be delayed when Ansible Core releases are. Subscribe to the Bullhorn for all future release dates, announcements, and Ansible contributor community news. To subscribe, visit the [Bullhorn category in the forum](https://forum.ansible.com/c/news/bullhorn/17) and click the `bell` button at the right side. Then select `Watching`. You can find all past Bullhorn issues on the Ansible Community Forum at: > **[Newsletter](https://forum.ansible.com/c/news/bullhorn/17)** > > This category holds the post archive from our newsletter, The Bullhorn. Subscribe to the category if you’d like a weekly roundup of news from the Ansible Ecosystem! ## Porting Help A unified porting guide for collections that have opted in is available here: [Ansible 11 Porting Guide — Ansible Community Documentation](https://docs.ansible.com/projects/ansible/devel/porting_guides/porting_guide_11.html) ## Getting collection updates from Ansible 11 with older releases of ansible-core Ansible 11 depends on ansible-core 2.18. Depending on your needs, you can get collection updates as they ship in the Ansible “batteries included” package while continuing to use older versions of ansible-core. See the ansible-galaxy requirements file based on the collections from Ansible 11 for this use case: [ansible-build-data/11/galaxy-requirements.yaml at 11.13.0 · ansible-community/ansible-build-data · GitHub](https://github.com/ansible-community/ansible-build-data/blob/11.13.0/11/galaxy-requirements.yaml) After you download the requirements file, you can install the collections by running the following command: ```console ansible-galaxy collection install -r galaxy-requirements.yaml ``` On behalf of the Ansible community, thank you and happy automating! Cheers, Ansible Release Management Working Group