Notre avis

Gère les releases de conteneurs Docker en mettant à jour les versions dans les fichiers de configuration et de documentation, et en relançant les workflows CI.

Points forts

Automatise la mise à jour des versions dans plusieurs fichiers simultanément
Réduit les erreurs manuelles lors des releases
S'intègre avec GitHub Actions pour le déploiement
Fourit un guide étape par étape clair

Limites

Fonctionne uniquement avec une structure de projet spécifique (GAIA)
Nécessite que VERSION.json et les README soient correctement configurés
Ne gère pas les conflits de branches ni les tags complexes

Quand l'utiliser

Lors de la publication de nouvelles versions de conteneurs Docker dans un projet standardisé avec VERSION.json et des README dédiés.

Quand l'éviter

Pour des projets sans fichier VERSION.json ou lorsque les releases nécessitent des branchements ou des tags avancés.

<release-skill> # Release Skill

Manage releases for GAIA Docker containers.

Usage

/release

Workflow

Read current versions from VERSION.json
Ask user for action:
- New Release: Bump version for gaia-linux, gaia-dev, or both
- Re-trigger Workflow: Re-publish current versions to Docker Hub
For New Release:
- Ask which container(s) to release
- Ask for new version number(s)
- Update VERSION.json
- Update hardcoded versions in README files
- Commit and push changes
For Re-trigger:
- Run gh workflow run to re-publish

Instructions

When the user invokes /release:

Step 1: Read Current State

Read VERSION.json to get current versions:

cat VERSION.json

Step 2: Ask User Intent

Use AskUserQuestion to ask:

"What would you like to do?"
- New gaia-linux release - Bump gaia-linux version
- New gaia-dev release - Bump gaia-dev version
- Re-trigger workflow - Re-publish current versions

Step 3a: For New Release

If user chose new release:

Ask for the new version number
Update VERSION.json with the new version
Update version references in these files:
- docs/gaia-linux/README.md - Update all occurrences of the old version
- docs/gaia-dev/README.md - Update all occurrences of the old version
- README.md - Update version in "Current Versions" line and examples
Commit changes with message: Release <container> v<version>
Push to main branch

Step 3b: For Re-trigger

If user chose re-trigger:

gh workflow run "Test, Publish, Release" --ref main

Then inform user that the workflow has been triggered and they can check progress at the Actions tab.

Files to Update on New Release

For gaia-linux release:

VERSION.json - Update "gaia-linux" value
docs/gaia-linux/README.md - Replace all gaia-linux:<old> with gaia-linux:<new>
README.md - Update "Current Versions" line and docker examples

For gaia-dev release:

VERSION.json - Update "gaia-dev" value
docs/gaia-dev/README.md - Replace all gaia-dev:<old> with gaia-dev:<new>
README.md - Update "Current Versions" line and docker examples

Example Interaction

User: /release

Claude: Current versions:
- gaia-linux: 0.15.3
- gaia-dev: 1.0.0

What would you like to do?
[New gaia-linux release] [New gaia-dev release] [Re-trigger workflow]

User: New gaia-linux release

Claude: What version should gaia-linux be released as?
Current: 0.15.3

User: 0.15.4

Claude: I'll update the following:
- VERSION.json: gaia-linux → 0.15.4
- docs/gaia-linux/README.md: Update version references
- README.md: Update version references

[Makes changes, commits, and pushes]

Done! Release v0.15.4 has been pushed. The CI workflow will:
1. Run tests
2. Build and push Docker images
3. Update Docker Hub README
4. Create GitHub release

Check progress: https://github.com/<repo>/actions

</release-skill>

Gestion des Releases Docker GAIA

Recommandé pour