release

Automates Ansible collection releases with changelog generation, tagging, and Galaxy publication.

8|7|Updated Feb 14, 2023
One-click install
npx skills add https://github.com/eclipse-slm/slm --skill release-eclipse-slm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/eclipse-slm/slm/tree/main/.agents/skills/release
Command: npx skills add https://github.com/eclipse-slm/slm --skill release-eclipse-slm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires antsibull-changelog.

What problem does it solve? Releasing an Ansible collection involves many error-prone manual steps: determining the next version from changelog fragments, generating changelogs with antsibull-changelog, creating release PRs, tagging, and publishing to Galaxy. This Skill guides the entire process with human confirmation gates to prevent mistakes. ## Core Features & Use Cases - Automatic Version Detection: Scans changelog fragment categories to determine whether the next release is a major, minor, or patch bump. - Ordered Release Workflow: Walks through changelog generation, release summary fragments, PR creation, tagging, GitHub releases, and Bullhorn announcements in the correct order. - Safety Gates: Requires explicit human confirmation before irreversible actions like pushing tags, and runs a security scan before release. - Use Case: A maintainer of an Ansible collection wants to ship version 2.1.0. The Skill reads galaxy.yml, detects minor-change fragments, generates the changelog, and produces every command needed through the GitHub release. ## Quick Start Ask the assistant to release a new version of this Ansible collection and it will determine the version and guide you through each step.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I release a new version of an Ansible collection?▼

Update the version in galaxy.yml, create a release summary fragment, run antsibull-changelog release, open a release PR, then tag and create a GitHub release after merge. This Skill automates that sequence with confirmation gates at each critical step.

How is the next Ansible collection version determined from changelog fragments?▼

Fragment categories map to semver bumps: breaking_changes or major_changes trigger a major bump, minor_changes or deprecated_features a minor bump, and bugfixes or trivial a patch bump. The highest-severity category found across all fragments wins.

What tools are required to run the Ansible collection release process?▼

You need antsibull-changelog installed via pip, the gh CLI authenticated with GitHub, push access to the upstream remote, and a git remote named upstream pointing to the canonical repository.

Why must the release summary fragment be created before running antsibull-changelog?▼

antsibull-changelog release processes and deletes all fragments when generating the changelog. If the release summary fragment does not exist beforehand, the summary will be missing from the generated CHANGELOG.rst.

Why are versions in changelog.yaml ordered incorrectly after a release?▼

antsibull-changelog can sort versions alphabetically, placing 10.x before 2.x. You must reorder the releases section semantically in changelogs/changelog.yaml and regenerate with antsibull-changelog generate.