# 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:** fedora, aap, 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:** 1

<div class="post-metadata">

**Author:** ![nitzmahone](https://avatars.discourse-cdn.com/v4/letter/n/c5a1d2/32.png) [@nitzmahone](https://forum.ansible.com/u/nitzmahone)\
**Post date:** [March 3, 2025, 9:43pm UTC](https://forum.ansible.com/t/core-2-19-templating-changes-preview-and-testing/40759/1 "2025-03-03T21:43:27Z")

</div>

## Background

Ansible Core 2.19 is slated to receive the [Data Tagging feature](https://github.com/ansible/ansible/pull/84621) we’ve been talking about and developing for several years. It’s been a long process, culminating in the largest set of changes to ansible-core since collections, including a significant overhaul of the templating engine and many other changes we’re hoping you’ll love. We’ve spent a lot of time validating countless backward compatibility scenarios, but a few of the security and templating changes may require adjustments to playbooks.

We’ve reached a point where we’re looking for community feedback and testing against pre-releases of ansible-core 2.19.

## How You Can Help

Right now, we’re hoping to get feedback around how well existing playbooks and content work with these new features. We’re still working on some plugin API changes and compatibility corner cases, as well as some new ways to more formally define the boundaries of those APIs.

The feature PR has merged and is available on ansible-core \>= 2.19.0b1, with continued stabilization leading up to the 2.19 release of ansible-core.

## Getting Help

Draft documentation for the new features can be found in the [2.19 porting guide](https://docs.ansible.com/ansible-core/devel/porting_guides/porting_guide_core_2.19.html), including detailed descriptions of the changes and example situations where content changes may be required.

## Reporting Issues

Issues specific to these changes should be filed with the [Pre-release Bug Report form](https://github.com/ansible/ansible/issues/new?template=pre_release.yml).

## Getting Started

There are two ways to test data tagging currently.

### Installing Using Pip

Install a current ansible-core pre-release from PyPI:

```shell
$ pip install --upgrade --pre 'ansible-core~=2.19.0b1'
...
$ ansible --version
ansible [core 2.19.0b1]
...

```

If the installation was successful, the version output should reflect a pre-release build of 2.19.

### Building Execution Environments

AAP/AWX Execution Environments can also be created with 2.19 pre-releases via ansible-builder 3.0+ using this method; use `ansible-core~=2.19.0b1` for the ansible\_core → package\_pip entry in the definition file and ensure that the Python interpreter is at least Python 3.1. For example:

```yaml
version: 3
images:
  base_image:
    name: registry.fedoraproject.org/fedora:41
dependencies:
  ansible_core:
    package_pip: ansible-core~=2.19.0b1
  ansible_runner:
    package_pip: ansible-runner
  python_interpreter:
    package_system: python3

```

---

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