# Core-2.19 templating changes - preview and testing

**URL:** <https://forum.ansible.com/t/core-2-19-templating-changes-preview-and-testing/40759>\
**Category:** Project Discussions\
**Tags:** aap, fedora, templating, awx, ansible-lint, ansible-core\
**Created:** [March 3, 2025, 9:43pm UTC](https://forum.ansible.com/t/core-2-19-templating-changes-preview-and-testing/40759 "2025-03-03T21:43:27Z")\
**Posts on this page:** 1\
**Showing post:** 30

<div class="post-metadata">

**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:** [May 7, 2025, 10:49am UTC](https://forum.ansible.com/t/core-2-19-templating-changes-preview-and-testing/40759/30 "2025-05-07T10:49:16Z")

</div>

I’m not disagreeing with what you write, but I wanted to link to [a post where the versioning scheme of ansible-core is explained](https://forum.ansible.com/t/42337). Basically every 2.x.0 release is a new major release in ansible-core’s versioning system. According to that the leading 2 will only get incremented if the internal architecture of ansible-core changes, which isn’t the case.

There also was some mention of retrospectively adding warnings to ansible-core 2.18 (or even earlier?) about implicit boolean conversion, but I don’t know what happened to that (I think @nitzmahone mentioned this on Matrix). Having that ASAP would improve the situation a lot.

---

_[View the full topic](https://forum.ansible.com/t/core-2-19-templating-changes-preview-and-testing/40759)._