In today's Ansible 9.6.0 release, we pinned community.grafana to <1.9.0 to avoid breaking changes.
Please amend this removal / breaking change and create a new 1.9.1 bugfix release without it as soon as possible, or risk freezing community.grafana to <1.9.0 for the remainder of the Ansible 9 release cycle.
The removal / breaking change was introduced here: #355 Better return the removed message argument until the next major release.
mariolenz
commented
1 month ago
SUMMARY
According to the changelog (https://github.com/ansible-collections/community.grafana/blob/main/CHANGELOG.rst#v190), the minor 1.9.0 release contains a removed feature which is a breaking change. This is explicitly prohibited by semantic versioning (https://semver.org/) - breaking changes must happen in new major versions.
Semantic versioning is one of the main collection requirements for inclusion in Ansible (https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_requirements.html#versioning-and-deprecation).
In today's Ansible 9.6.0 release, we pinned community.grafana to <1.9.0 to avoid breaking changes.
Please amend this removal / breaking change and create a new 1.9.1 bugfix release without it as soon as possible, or risk freezing community.grafana to <1.9.0 for the remainder of the Ansible 9 release cycle.
The removal / breaking change was introduced here: #355 Better return the removed
messageargument until the next major release.ISSUE TYPE