# Ansible-core devel and milestone bumped to 2.21.0.dev0

**URL:** <https://forum.ansible.com/t/ansible-core-devel-and-milestone-bumped-to-2-21-0-dev0/44684>\
**Category:** Collection Development\
**Tags:** news-for-maintainers, ci, collections, ansible-core\
**Created:** [October 15, 2025, 5:49am UTC](https://forum.ansible.com/t/ansible-core-devel-and-milestone-bumped-to-2-21-0-dev0/44684 "2025-10-15T05:49:00Z")\
**Posts on this page:** 1\
**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:** [October 15, 2025, 5:49am UTC](https://forum.ansible.com/t/ansible-core-devel-and-milestone-bumped-to-2-21-0-dev0/44684/1 "2025-10-15T05:49:00Z")

</div>

ansible-core’s `devel` and `milestone` branch versions have been bumped to 2.21.0.dev0. If you are a collection maintainer, you need to consider:

1. If you test against `devel` or `milestone` and have a `tests/sanity/ignore-2.20.txt` file, you need to copy it over to `tests/sanity/ignore-2.21.txt`;
2. Update your CI matrix to include `stable-2.20` if you didn’t do that already; if you did not test against `devel` before, potentially need to create a `tests/sanity/ignore-2.20.txt` file.
