ansible-build-data
ansible-build-data copied to clipboard
Holds generated but persistent results from building the ansible community package
The indents in the release workflow were different for different parts of the file. This fixes it, and adds a yamllint step for the whole repository. The automatically generated/updated files...
As per https://github.com/ansible-community/ansible-build-data/blob/main/docs/policies.md#enforcement, we need to track violations of the [Repository management](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_requirements.html#repository-management) policies. We also need to track violations when [collection dependencies conflicts arise](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_requirements.html#collection-dependencies), or collections violate [semantic versioning](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_requirements.html#versioning-and-deprecation) by...
We should have the tag workflow query the Github API for the merged release PR's commit hash instead of just tagging the HEAD of the main branch.
This way, the release manager could commit other changes prior to running the release GHA while still having those changes included in the PR.
Based on comments of @gotmax23 in the #release-management:ansible.com room.
Ideally, we should set up this workflow to automatically create an ansible-documentation PR to copy over the release notes. We'll probably need to set up a bot user for this....
Remove netapp.storagegrid from Ansible 11 as discussed in [Unmaintained collection: netapp.storagegrid](https://forum.ansible.com/t/2811) and announced in #372.
Remove inspur.sm from Ansible 11 as discussed in [Unmaintained collection: inspur.sm](https://forum.ansible.com/t/2854) and announced in #362.
Since we've had some typos etc in recent release announcements for the Ansible package, the idea surfaced to create a GitHub Actions that would take the template announcements being created...
Relates to https://github.com/ansible-collections/ansible-inclusion/discussions/65 The renaming process is described in [README](https://github.com/ansible-community/ansible-build-data/#renaming-a-collection) For simplicity, assume that the next minor Ansible release is X.Y.0, and that collection foo.bar with latest release a.b.c has...