# Ansible-core devel bumped to 2.19.0.dev0, stable-2.18 branch created

**URL:** <https://forum.ansible.com/t/ansible-core-devel-bumped-to-2-19-0-dev0-stable-2-18-branch-created/8723>\
**Category:** Collection Development\
**Tags:** news-for-maintainers, ci, collections, ansible-core\
**Created:** [September 24, 2024, 10:09am UTC](https://forum.ansible.com/t/ansible-core-devel-bumped-to-2-19-0-dev0-stable-2-18-branch-created/8723 "2024-09-24T10:09:19Z")\
**Posts on this page:** 2\
**Page:** 1

<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:** [September 24, 2024, 10:09am UTC](https://forum.ansible.com/t/ansible-core-devel-bumped-to-2-19-0-dev0-stable-2-18-branch-created/8723/1 "2024-09-24T10:09:19Z")

</div>

ansible-core’s `devel` branch’s version has been bumped to 2.19.0.dev0, and a `stable-2.18` branch has been created. If you are a collection maintainer, you need to consider:

1. If you test against `devel` and have a `tests/sanity/ignore-2.18.txt` file, you need to copy it over to `tests/sanity/ignore-2.19.txt`;
2. Update your CI matrix to include `stable-2.18`; if you did not test against `devel` before, potentially need to create a `tests/sanity/ignore-2.18.txt` file.

---

<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:** [September 24, 2024, 10:46am UTC](https://forum.ansible.com/t/ansible-core-devel-bumped-to-2-19-0-dev0-stable-2-18-branch-created/8723/2 "2024-09-24T10:46:25Z")

</div>

Note that `stable-2.18` has [Remove remaining 2.18 deprecations by sivel · Pull Request #83949 · ansible/ansible · GitHub](https://github.com/ansible/ansible/pull/83949), which `devel` does not. This make some tests fail in community.crypto for stable-2.18, while they pass for `devel`, `stable-2.17`, and other stable branches. From the comments in the PR the tests will also start failing with `devel` eventually, so if you see similar failures with `stable-2.18`, you can assume that the same tests will start failing with `devel` as well eventually.