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 exactly 3 files. Usingv0.17.0 as an example:
1. src/gaia/version.py — bump __version__
2. docs/releases/v0.17.0.mdx — create release notes
Create a new file with MDX frontmatter and the 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):
"releases/v0.17.0" as the second entry (after "releases/index", before the previous release).
(b) Update the navbar version label:
label value to match the new release tag.
Merge, tag, push
After the PR is merged:CI validation
ThePublish 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 |
- The release notes content is published to GitHub Releases
- The package is published to PyPI