Skip to content
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

cisco.dnac 6.10.0 is not tagged #142

Closed
Tracked by #223
felixfontein opened this issue Dec 20, 2023 · 2 comments · Fixed by ansible-community/ansible-build-data#348
Closed
Tracked by #223

cisco.dnac 6.10.0 is not tagged #142

felixfontein opened this issue Dec 20, 2023 · 2 comments · Fixed by ansible-community/ansible-build-data#348

Comments

@felixfontein
Copy link

Hi! As part of the ansible community package release process, we've determined that version 6.10.0 of cisco.dnac 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.

@fmunozmiranda
Copy link
Collaborator

Hi @felixfontein tag and realease included to repo.

@felixfontein
Copy link
Author

@fmunozmiranda thanks! I created ansible-community/ansible-build-data#348 to remove the constraint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants