Copied from ansible-community/ansible-build-data#538

ansible-core has implemented an extensive rewrite of templating and error handling as part of the data tagging feature coming in core-2.19. You can find information about this change in that PR description, as well as in the core 2.19 porting guide.

Please read background and testing requests, which details where you can file potential bugs.

Collections that are part of the Ansible community package MUST test against ansible-core 2.19 to ensure they continue to work with the updated core. Collections which are not compatible with ansible-core 2.19 will be removed from Ansible 12. You can choose to test against the stable-2.19 branch, the devel branch, the milestone branch, or the pre-release/released versions of ansible-core 2.19 available on Pypi.

This should be an ongoing verification/check until the release of core 2.19 to ensure compatibility with any bugfixes or changes that happen until then.

You can find advice from fellow maintainers at Making a collection compatible with data tagging, and we welcome your additions to that forum topic.

Note: You are not required to implement data tagging as part of this request, though we do recommend you consider where it can improve the quality of your collection. This issue is focused on ensuring you have verified your collection works with ansible-core 2.19 in order to remain included in the Ansible 12 community package.

We ask that you resolve any problems and link those PRs to this issue. If you do not find any problems with your integration/unit testing, please provide that comment and a pointer to your test results before closing this issue as done.

You can reach out on the Ansible forum for more help or discussion.