Ansible-core 2.18.0 Released, Marking Feature Freeze for Ansible 11 Collections

Ansible-core 2.18.0 has been officially released today, November 4, 2026. This release is significant as it also marks the final day for collections to introduce backwards-incompatible changes if they are to be accepted into the forthcoming Ansible 11.0.0 community package. Following this, Ansible 11.0.0 beta1 is slated for release tomorrow, November 5, 2026, initiating a feature freeze for the community package. This development is crucial for anyone deeply involved with Ansible, from core developers to system administrators and DevOps engineers. The stabilization of Ansible-core 2.18.0 provides a firm foundation for the next major iteration of the Ansible community package. For collection maintainers, missing this deadline means their breaking changes will have to wait for Ansible 11.1.0 or later, potentially delaying feature adoption for users. For end-users, it means that the core engine they rely on for automation is now locked in, and the focus will shift to how their existing playbooks and roles interact with the new core and the integrated collections in Ansible 11. This release aligns with the broader trend in open-source project development where core components are stabilized before integrating a wider ecosystem of modules and extensions. This phased approach allows for rigorous testing and refinement of the foundational elements, ensuring a more robust and reliable platform for subsequent releases. The emphasis on clear release schedules and deprecation policies, though not always guaranteed, reflects a mature project striving for predictability in a rapidly evolving automation landscape. Practitioners should immediately begin reviewing their custom or third-party Ansible collections against Ansible-core 2.18.0 to identify any potential incompatibilities. While the Ansible 11.0.0 beta will offer an opportunity for testing, proactive validation now can prevent disruptions. Developers of collections should ensure all necessary backwards-incompatible changes are submitted today. For those planning upgrades, understanding the new core's capabilities and any changes to included collections will be paramount to a smooth transition to Ansible 11. It's also a good time to engage with the Ansible community forums for discussions around potential breaking changes and best practices for migration.