You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! As part of the ansible community package release process,
we've determined that version 2.0.1 of inspur.sm 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.
The text was updated successfully, but these errors were encountered:
Hi! As part of the ansible community package release process,
we've determined that version 2.0.1 of inspur.sm was 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.
The text was updated successfully, but these errors were encountered: