stable-release-analyze

Run the analyze-collection.py script against your collection path. It detects all stable-X branches, counts commits since the last tag, and reports which branches need releases with the recommended next version.

Fragment types map to impact levels: breaking_changes and removed_features trigger a MAJOR bump, major_changes, minor_changes, and deprecated_features trigger MINOR, and bugfixes or security_fixes trigger PATCH. The highest impact across all fragments wins.

You need Python 3.8+, PyYAML (auto-installed in a virtual environment), a git repository with a configured upstream remote, stable branches following the stable-X naming convention, and a galaxy.yml file in the collection root.

This warning appears when a stable branch has unreleased commits but the changelogs/fragments directory is missing or empty. Add changelog fragment YAML files describing the changes before proceeding with the release.

Set the REMOTE_UPSTREAM environment variable to origin, optionally in ~/.ansible-release.conf. The skill defaults to the standard fork-and-pull convention where upstream is the canonical repository.