search

cyberark / ansible-security-automation-collection

CyberArk Ansible Security Automation Collection
MIT License
60 stars 37 forks source link

cyberark.pas 1.0.27 is not tagged #71

Closed felixfontein closed 1 month ago

felixfontein commented 4 months ago

Summary

Hi! As part of the ansible community package release process, we've determined that version 1.0.27 of cyberark.pas was released to Ansible Galaxy but not properly tagged in this Git repository. This violates the repository management section of the Collection Requirements:

Every collection MUST have a public git repository. Releases of the collection MUST be tagged in said repository. This means that releases MUST be git taged and that the tag name MUST exactly match the Galaxy version number. Tag names MAY have a v prefix, but a collection's tag names MUST have a consistent format from release to release.

Additionally, collection artifacts released to Galaxy MUST be built from the sources that are tagged in the collection's git repository as that release. Any changes made during the build process MUST be clearly documented so the collection artifact can be reproduced.

If the collection maintainers do not respond to this issue within a reasonable a amount of time, the collection is subject to Removal from ansible.

szh commented 4 months ago

@cyberark-bizdev why is this happening again?

felixfontein commented 3 months ago

@szh @cyberark-bizdev any update on this? It's still not tagged: https://github.com/cyberark/ansible-security-automation-collection/tags

szh commented 3 months ago

I've ping them internally. This is managed by our bizdev department, not R&D (which I'm in), and I have very little visibility into how they work.

felixfontein commented 1 month ago

The 1.0.27 tag has been added in the meantime. I don't know when that happened, but not mentioning it here resulted in the constraint not being removed, and thus 1.0.27 not being included in the last Ansible release(s), even if the tag was already around by then.