-
Notifications
You must be signed in to change notification settings - Fork 37
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
Collection Requirements Violation - Repository Management (2) #58
Collection Requirements Violation - Repository Management (2) #58
Comments
* 8: pin cyberark.pas due to tagging policy violation Relates: cyberark/ansible-security-automation-collection#58 * 7: pin cyberark.pas due to tagging policy violation Relates: cyberark/ansible-security-automation-collection#58
@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. |
I tagged the releases |
Please let me know if anything else needs to be done |
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. |
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:
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 #46 and the collection is again violating this requirement.
The text was updated successfully, but these errors were encountered: