Release ansible-support project as collection on Ansible Galaxy #266

Closed
opened 2026-09-20 10:02:32 +00:00 by brettweir · 3 comments
Member

Here are all the steps I've identified to release ansible-support as an Ansible collection. Some of these things are not strictly required but help to ensure higher quality releases. I'm going to aim for all of them but with a goal of fully releasing within the next couple of weeks.

  • Claim Ansible Galaxy namespace
  • Remove unneeded files
  • Add Ansible Galaxy metadata
  • Add ForgeJo workflows
    • Add Ansible lint workflow
    • Add Ansible collection release workflow with version injection
  • Clean up unrelated Git history
  • Adopt final collection name
  • Add collection README.md
  • Cut 0.1.0 release
Here are all the steps I've identified to release ansible-support as an Ansible collection. Some of these things are not strictly required but help to ensure higher quality releases. I'm going to aim for all of them but with a goal of fully releasing within the next couple of weeks. - [x] Claim Ansible Galaxy namespace - [x] Remove unneeded files - [x] Add Ansible Galaxy metadata - [x] Add ForgeJo workflows - [x] Add Ansible lint workflow - [x] Add Ansible collection release workflow with version injection - [x] Clean up unrelated Git history - [x] Adopt final collection name - [x] Add collection README.md - [x] Cut 0.1.0 release
Author
Member
- Claimed `fedoraserver` namespace - Some cleanup with https://forge.fedoraproject.org/server/ansible-support/pulls/189 - Working name is `fedoraserver.general` - Lint job from https://forge.fedoraproject.org/server/ansible-support/pulls/188
Author
Member
  • There's now an Ansible build/publish workflow
- There's now an Ansible build/publish workflow
Author
Member

Created separate issue for follow-up CI/CD activities.

Created separate issue for follow-up CI/CD activities.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
server/tickets#266
No description provided.