-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tracker] Serious collection requirements violations that require version pinning #223
Comments
cyberark.pas is again violating this guideline (#235 (comment)). I filed cyberark/ansible-security-automation-collection#58. |
dellemc.enterprise_sonic needs to be pinned to 2.0.0 in both Ansible 7 and Ansible 8 for two violations:
|
hetzner.hcloud needs to be pinned to 1.11.0 in both Ansible 7 and 8 for a semantic versioning violation: ansible-collections/hetzner.hcloud#217 |
There has been a new release of dellemc.enterprise_sonic (2.2.0) which reverts the breaking change and declares compatibility with |
The issue with hetzner.hcloud is resolved (ansible-collections/hetzner.hcloud#217, #267). |
|
|
cisco.meraki moved to a new repository: https://github.com/meraki/dashboard-api-ansible - I'll create PRs for ansible-build-data to adjust it. |
cisco.intersight was now tagged, #289 removed the ignore for the missing tags. |
|
|
Resolved - poor usage of flag in the changelog. Changelogs fixed and new Collection version released |
This reverts commit 6fd2b9d. Ref: ansible-community#223 (comment)
This reverts commit 6fd2b9d. Ref: #223 (comment)
|
|
|
|
community.ciscosmb introduced a breaking change in 1.0.8: ansible-collections/community.ciscosmb#75 |
It looks like frr.frr fails a lot of tests. I don't care about the unit tests but the failing sanity tests are problematic. I've opened ansible-collections/frr.frr#66 to let them know. |
community.grafana introduced a breaking change (removed feature) in 1.9.0: ansible-collections/community.grafana#367 |
cyberark.pas 1.0.27 is not tagged: cyberark/ansible-security-automation-collection#71 |
It's too late for version pinning since 2.6.0 of that collection has been included for some months now, but FYI: CiscoDevNet/ansible-mso#479 - I've created https://forum.ansible.com/t/7039 for this. |
As per https://github.com/ansible-community/ansible-build-data/blob/main/docs/policies.md#enforcement, we need to track violations of the Repository management policies. We also need to track violations when collection dependencies conflicts arise, or collections violate semantic versioning by doing breaking changes outside of major versions. When you file an issue against a collection for violating these policies, leave a comment with a link to the issue.
The text was updated successfully, but these errors were encountered: