# \[ACTION REQUIRED for Ansible package-included collections\] CI: Add test runs against devel or milestone branch of ansible-core

**URL:** <https://forum.ansible.com/t/action-required-for-ansible-package-included-collections-ci-add-test-runs-against-devel-or-milestone-branch-of-ansible-core/45599>\
**Category:** News & Announcements\
**Tags:** news-for-maintainers, ansible-test, collections\
**Created:** [March 26, 2026, 10:57am UTC](https://forum.ansible.com/t/action-required-for-ansible-package-included-collections-ci-add-test-runs-against-devel-or-milestone-branch-of-ansible-core/45599 "2026-03-26T10:57:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [March 26, 2026, 10:57am UTC](https://forum.ansible.com/t/action-required-for-ansible-package-included-collections-ci-add-test-runs-against-devel-or-milestone-branch-of-ansible-core/45599/1 "2026-03-26T10:57:40Z")

</div>

The Ansible community and its steering committee have discussed and introduced a new Ansible community package collection inclusion requirement.

If you maintain a collection included in the Ansible community package, please add testing against the `devel` or `milestone` branches of ansible-core if you aren’t already doing so.

Specifically, you **MUST do ONE OF** the following:

- Run tests against the `devel` or `milestone` branch of `ansible-core` in every PR. You can use [collection\_template/.github/workflows/ansible-test.yml](https://github.com/ansible-collections/collection_template/blob/main/.github/workflows/ansible-test.yml) to get started.
- Run tests on a scheduled basis of at least once per week to avoid occasional unrelated failures in every PR after `ansible-core` introduces new checks. You can use the [workflow](https://github.com/ansible-collections/collection_template/blob/main/.github/workflows/ansible-test.yml) to run it only against `devel` or `milestone` and only on “schedule: …” by removing everything else.

This requirement ensures that you find out about new linting requirements and compatibility issues between your collection and `ansible-core` early.

See the [pull request](https://github.com/ansible/ansible-documentation/pull/3511) and the [discussion](https://forum.ansible.com/t/vote-ended-2026-03-26-collection-inclusion-requirements-update-proposal-mandate-testing-against-devel-or-milestone-branch-of-ansible-core/45486) for details.

Collections that do not test against `devel` or `milestone` will not be removed immediately. However, because this is a package inclusion requirement, the removal process can be initiated at some point in the near future with prior notification.

Thank you!