current-release

Determines the current release version from git tags, stable branches, or galaxy.yml.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Determining the current published version of an Ansible collection is error-prone when version information is scattered across git tags, stable branches, and galaxy.yml. This Skill resolves the correct current version automatically, including detecting when a branch may be behind a released version. ## Core Features & Use Cases - Multi-source version detection: Reads the latest version from git tags on stable branches and from the version field in galaxy.yml, then compares them with a defined algorithm. - Development status reporting: Strips -dev0 suffixes to report a baseline version and indicates whether the version is IN DEVELOPMENT or RELEASED. - Stale branch warning: Flags when a newer version appears to have been released than the one in galaxy.yml, prompting a rebase check for backport or older-branch work. - Use Case: Before writing a changelog entry or version_added tag, ask for the current version to confirm whether main is developing the next major, minor, or patch release. ## Quick Start Ask the AI what the current release version of this collection is.

Frequently Asked Questions about current-release

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

FAQPage Schema
How do I find the current release version of an Ansible collection?▼

Check the highest git tag matching the latest stable-N branch and compare it with the version field in galaxy.yml. The higher of the two, after stripping any -dev0 suffix, is the current baseline version.

How to compare versions with -dev0 suffixes in galaxy.yml?▼

Strip the -dev0 suffix from both versions, split each into major, minor, and patch numbers, then compare numerically in that order. For example, 9.2.0 versus 10.0.0-dev0 resolves to 10.0.0 being higher.

What does it mean when galaxy.yml version is lower than the latest git tag?▼

It indicates a newer version was released after the branch was created, so the branch may need a rebase. For intentional backport or older-branch work, the galaxy.yml version can still be used.

Does this version detection work without stable branches?▼

Yes, when no stable-N branches exist, the version is read directly from galaxy.yml. A -dev0 suffix means the version is in development; otherwise it is treated as released.

When should I check the current version during release work?▼

Check it before writing changelog entries, setting version_added tags, or planning the next release. It confirms whether main is developing the next major, minor, or patch version relative to the latest stable branch.