This week in Ansible Community
Issue #232, 2026-06-26 (Past Issues)
Welcome to The Bullhorn, our newsletter for the Ansible Community. If you have any questions or content you’d like to share, you’re welcome to chat with us in the Ansible Social room on Matrix, and mention newsbot to have your news item tagged for review for the next weekly issue!
Project updates 
Felix Fontein contributed
The GitHub - ansible-community/ansible-test-gh-action: A composite GitHub Action encapsulating the GitHub Actions CI/CD workflows setup necessary for testing Ansible collection repositories on GitHub · GitHub action (GitHub - ansible-community/ansible-test-gh-action: A composite GitHub Action encapsulating the GitHub Actions CI/CD workflows setup necessary for testing Ansible collection repositories on GitHub · GitHub) has a new release, version 1.18.0 (Release v1.18.0 · ansible-community/ansible-test-gh-action · GitHub). This new release has updated dependencies, supports ansible-core 2.20 and 2.21, and changed the default ansible-core version to 2.21.
Collection updates 
andersson007_ shared
The ansible.mysql collection version 5.1.0 has been released!
David Buckman shared
The community.rabbitmq collection version 1.7.0 has been released!
This release announces the following breaking changes that will arrive in the 2.0.0 release:
- RabbitMQ versions prior to 3.7.0 will be deprecated
- Python 2 support will be depricated
- Minimum supported ansible-core version will be 2.16
Other events and releases
Use the Ansible Forum to see other events and releases.
Join the Ansible community
Looking for ways to get involved? See how can I help for some ideas!
You can find easy issues in collections and other projects for code or documentation contributions.
That’s all for now!
Have any questions you’d like to ask, or issues you’d like to see covered? Please ask in #social:ansible.com! See you next time!