Collection Requirements Violation - Repository Management (2)

[gotmax23]

Hi! As part of the ansible community package release process, we've determined that versions 1.0.18 and 1.0.19 of cyberark.pas were 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.

Note that we've already reported this issue once in https://github.com/cyberark/ansible-security-automation-collection/issues/46 and the collection is again violating this requirement.

[szh]

@cyberark-bizdev Please see https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits for signing commits. Also the releases should be tagged in git and released in GitHub.

[cyberark-bizdev]

I tagged the releases

[cyberark-bizdev]

Please let me know if anything else needs to be done

[gotmax23]

Nope, it looks good to me. Thanks! Please make sure that tagging releases is a regular part of the release process so this doesn't happen again.