Cisco.ucs 1.16.0 violates ACP requirements

Project Discussions
, ,
1

I think that cisco.ucs violates our requirements for CI Testing:

  1. As far as I can see, sanity tests don’t include ansible-core 2.20 currently. (Actually, I think they should have added even 2.21 by now.)
  2. And, anyway, the last CI run seems to have been Jun 30, 2025.

What should we do about this?

2

I guess the best would be to create an issue in the collection’s repo and see whether there’s a reply.

Maybe we should start a tracker similar to the one in [Tracker] Serious collection requirements violations that require version pinning · Issue #223 · ansible-community/ansible-build-data · GitHub that’s for “other” violations that do not block inclusion in a release. Anyone has a good idea where such a tracker should stay? The issue is OK for tracking things that don’t happen too often, but general violations might be more common. Maybe we should use an issue board where we can attach issues from various repos? (Does that actually trigger notifications, i.e. when an issue is added, moved to another column, …?)