Ansible project 10.0

This release schedule includes dates for the ansible package, with a few dates for the ansible-core package as well. All dates are subject to change. See the ansible-core 2.17 Roadmap for the most recent updates on ansible-core.

Release schedule


ansible-core feature freeze, stable-2.17 branch created.


Start of ansible-core 2.17 betas


Ansible-10.0.0 alpha1 [1]


First ansible-core 2.17 release candidate.


Ansible-10.0.0 alpha2 [1]


Ansible-core-2.17.0 released.


Last day for collections to make backwards incompatible releases that will be accepted into Ansible-10. This includes adding new collections to Ansible 10.0.0; from now on new collections have to wait for 10.1.0 or later.


Ansible-10.0.0 beta1 – feature freeze [2] (weekly beta releases; collection owners and interested users should test for bugs).


Ansible-10.0.0 rc1 [3] [4] (weekly release candidates as needed; test and alert us to any blocker bugs). Blocker bugs will slip release.


Last day to trigger an Ansible-10.0.0rc2 release because of major defects in Ansible-10.0.0rc1.


Ansible-10.0.0rc2 when necessary, otherwise Ansible-10.0.0 release.


Ansible-10.0.0 release when Ansible-10.0.0rc2 was necessary.

2024-06-04 or 2023-06-11:

Create the ansible-build-data directory and files for Ansible-11.


Release of ansible-core 2.17.1.


Release of Ansible-10.1.0 (bugfix + compatible features: every four weeks.)


Breaking changes will be introduced in Ansible 10.0.0. We encourage the use of deprecation periods that give advance notice of breaking changes at least one Ansible release before they are introduced. However, deprecation notices are not guaranteed to take place.


In general, it is in the discretion of the release manager to delay a release by 1-2 days for reasons such as personal (schedule) problems, technical problems (CI/infrastructure breakdown), and so on. However, in case two releases are planned for the same day, a release of the latest stable version takes precedence. This means that if a stable Ansible 10 release collides with a pre-release of Ansible 11, the latter will be delayed. If a Ansible 10 release collides with a stable Ansible 11 release, including 11.0.0, the Ansible 10 release will be delayed.

Planned major changes

You can install removed collections manually with ansible-galaxy collection install <collection_name>.

Ansible minor releases

Ansible 10.x follows ansible-core-2.17.x releases, so releases will occur approximately every four weeks. If ansible-core delays a release for whatever reason, the next Ansible 10.x minor release will be delayed accordingly.

Ansible 10.x minor releases may contain new features (including new collections) but not backwards incompatibilities. In practice, this means we will include new collection versions where either the patch or the minor version number has changed but not when the major number has changed. For example, if Ansible-10.0.0 ships with community.crypto 2.3.0, Ansible-10.1.0 could ship with community.crypto 2.4.0 but not community.crypto 3.0.0.


Minor and patch releases will stop when Ansible-11 is released. See the Release and Maintenance Page for more information.


We will not provide bugfixes or security fixes for collections that do not provide updates for their major release cycle included in Ansible 10.

For more information, reach out on a mailing list or a chat channel - see Communicating with the Ansible community for more details.