GAIA Docker Release Management

VerifiedSafe

Manages releases for GAIA Docker containers. Reads current versions from VERSION.json, supports bumping versions for gaia-linux or gaia-dev with automatic file updates, or re-triggering the publish workflow.

Sby Skills Guide Bot
DevelopmentIntermediate
706/2/2026
Claude Code
#release-management#docker#versioning#ci

Recommended for

Our review

Manages Docker container releases by bumping versions in configuration and documentation files, and re-triggering CI workflows.

Strengths

  • Automates version bumps across multiple files simultaneously
  • Reduces manual errors during releases
  • Integrates with GitHub Actions for deployment
  • Provides clear step-by-step guidance

Limitations

  • Only works with a specific project structure (GAIA)
  • Requires proper setup of VERSION.json and README files
  • Does not handle branch conflicts or complex tagging
When to use it

When releasing new versions of Docker containers in a standardized project with VERSION.json and dedicated README files.

When not to use it

For projects without a VERSION.json file or when releases require advanced branching or tagging.

Security analysis

Safe
Quality score92/100

The skill only reads version files and updates them with user-supplied version numbers; the only command that interacts with external systems is 'gh workflow run', which triggers a predefined CI workflow and does not run arbitrary destructive commands or exfiltrate data.

No concerns found

Examples

Trigger release workflow
/release
<release-skill> # Release Skill

Manage releases for GAIA Docker containers.

Usage

/release

Workflow

  1. Read current versions from VERSION.json
  2. 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
  3. 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
  4. 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:

  1. Ask for the new version number
  2. Update VERSION.json with the new version
  3. 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
  4. Commit changes with message: Release <container> v<version>
  5. 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>
Related skills