# Release history, cli.sgit.ai

> Every release of cli.sgit.ai, newest first, with one sentence on what changed and why.

*Source: <https://cli.sgit.ai/admin/versions.html> · generated from the same content as the page, so the two cannot drift.*

---
# Release history

The site's version is in `admin/build/version.txt` and goes up on every push to `dev`; the badge at the top of every page reads it. The command reference carries its own version, the sgit-ai release it was generated from.

| Version | Date | Command reference | What changed, and why |
|---|---|---|---|
| v0.1.2 | 2026-10-20 | sgit-ai v0.23.0 | The reality file catches up: cli.sgit.ai was checked live after v0.1.1 deployed (DNS, Pages and the `dev` environment all work), so it moves from "does not exist yet" to "exists". |
| v0.1.1 | 2026-10-20 | sgit-ai v0.23.0 | The generator and the gate reach the repository: the Python `.gitignore` template's `build/` rule had kept `admin/build/` out of the v0.1.0 commit, so CI could not run `validate.js` and nothing deployed. `.gitignore` now re-includes `admin/build/`. |
| v0.1.0 | 2026-10-20 | sgit-ai v0.23.0 | The first version, built from [the brief](../briefs/index.md) the same day: 27 pages moved from sgit.ai (site v0.7.87) so the CLI's technical documentation has one home, the command reference generated from `sgit help all --format json` (158 commands), and 23 research documents from the CLI repository (`SGit-AI__CLI` at 5597526) published as articles, with the generator, the gate and the deploy pipeline the sibling sites run. |

---

*[Site index for agents](../llms.txt) · [HTML version](https://cli.sgit.ai/admin/versions.html)*