Release Notes

Browse the full release history for GAIA below, or on GitHub Releases. Each release includes a summary of new features, improvements, bug fixes, and upgrade instructions.

Release Process

GAIA follows a release-notes-first workflow. All release artifacts are prepared and reviewed in a PR before the tag is pushed.

Files to update

Every release PR must update 5 files. Using v0.17.0 as an example:

1. `src/gaia/version.py` — bump `version`

# before
__version__ = "0.16.1"

# after
__version__ = "0.17.0"

2. `docs/releases/v0.17.0.mdx` — create release notes

Create a new file with MDX frontmatter and the required sections:

---
title: "v0.17.0"
description: "Short one-line summary of this release"
---

# GAIA v0.17.0 Release Notes

Summary paragraph describing the release.

## What's New

### Feature Name
Description of the feature.

## Bug Fixes

- **Description**: What was fixed

## Full Changelog

Full Changelog: [v0.16.1...v0.17.0](https://github.com/amd/gaia/compare/v0.16.1...v0.17.0)

Required sections: ## What's New (or ## Key Changes) and ## Full Changelog, plus a github.com/amd/gaia/compare/ link.

3. `docs/docs.json` — two changes

(a) Add the release to the Releases tab pages array (newest first):

{
  "tab": "Releases",
  "groups": [{
    "group": "Release Notes",
    "pages": [
      "releases/index",
      "releases/v0.17.0",
      "releases/v0.16.1"
    ]
  }]
}

Add "releases/v0.17.0" as the second entry (after "releases/index", before the previous release). (b) Update the navbar version label:

{
  "navbar": {
    "links": [
      {
        "label": "v0.17.0 · Lemonade 10.0.0",
        "href": "https://github.com/amd/gaia/releases"
      }
    ]
  }
}

Change the version in the label value to match the new release tag.

4. `hub/components/terminal-hub/gaia-agent.yaml` — bump `version` and `min_gaia_version`

The terminal’s six raw binaries publish to the Agent Hub (R2), where the flagship agent’s lock pins them, and release_components.yml gates a tag against this manifest — publishing under a stale version fails the release, since R2 paths are immutable. The installers and the desktop app ship on the GitHub release only, so hub/components/agent-ui/ is no longer published and needs no bump.

5. `src/gaia/apps/webui/package.json` and `package-lock.json` — bump the UI version

Run node installer/version/bump-ui-version.mjs after src/gaia/version.py is updated; it reads the new version from there and rewrites both files.

Merge, tag, push

After the PR is merged:

git tag v0.17.0
git push origin v0.17.0

CI validation

The Publish GAIA Release workflow runs a validate-release job that blocks the release if any check fails:

Check	What it validates
Release notes exist	`docs/releases/v0.17.0.mdx` is present
Version consistency	`__version__` in `src/gaia/version.py` equals `0.17.0`
docs.json release entry	`releases/v0.17.0` is in the Releases tab pages array
docs.json navbar	Navbar label contains `v0.17.0`
Release notes structure	Has frontmatter (`title`, `description`), required sections, and changelog link

If all checks pass:

The release notes content is published to GitHub Releases
The package is published to PyPI

​Release Notes

​Release Process

​Files to update

​1. src/gaia/version.py — bump __version__

​2. docs/releases/v0.17.0.mdx — create release notes

​3. docs/docs.json — two changes

​4. hub/components/terminal-hub/gaia-agent.yaml — bump version and min_gaia_version

​5. src/gaia/apps/webui/package.json and package-lock.json — bump the UI version

​Merge, tag, push

​CI validation