gaia-release

Bump the GAIA version, commit, tag, push, and publish a GitHub Release.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-release
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-release
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GAIA's release process for the framework involves multiple manual steps that are error-prone and time-consuming. This skill provides a repeatable, auditable workflow to bump versions, commit changes, create Git tags, push to remotes, and publish GitHub releases from the main branch. It centralizes policy and tooling so release engineers and developers can consistently release new GAIA versions without drift.

Core Features & Use Cases

  • Version bumping via scripts/version-bump.js to keep package.json and framework_version in sync.
  • Automated Git operations: commit, tag, and push with deterministic outputs.
  • GitHub Release generation and publishing to provide release notes alignment.
  • Enforces main-branch policy and dry-run validations to prevent accidental releases.
  • Ensures a single source of truth for versioning and release artifacts across the project.

Quick Start

Run a dry-run to preview the new version and changed files, then execute the real release using the release script.

Frequently Asked Questions about gaia-release

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

FAQPage Schema
How do I automate a GitHub release from version bump to publish?

Automating a GitHub release involves bumping the version, committing changes, tagging, pushing to remotes, and publishing the release notes. This skill executes these deterministic steps sequentially to prevent manual errors.

Can I preview version bump changes before committing to a Git release?

Yes, you can run a dry-run validation to preview the new version and changed files. This enforces main-branch policies and prevents accidental releases before executing the actual publish workflow.

How do I keep package.json and framework_version in sync during a release?

Keeping package.json and framework_version in sync requires a single source of truth for versioning. The process uses a dedicated version-bump script to update both files simultaneously during the release workflow.

Does the Git release workflow enforce a specific branch policy?

Yes, the release workflow enforces a strict main-branch policy. It ensures deterministic outputs and validates all versioning steps against the main branch to prevent drift across the project.

What is the best way to prevent drift in framework versioning across releases?

Preventing versioning drift requires centralizing release policies and tooling. Using a repeatable, auditable workflow with deterministic script validation ensures a single source of truth for all framework release artifacts.