# sgit-ai 0.26.12.dev0: dev builds are pre-releases again; sgit update follows the channel, cli.sgit.ai

> Dev build of 28 October 2026, from the CLI's dev at 9346851d: the first build published as a PEP 440 pre-release (X.Y.Z.devN), so a plain pip install never selects it and pip install --pre does. The CLI team is yanking the eleven plain dev versions 0.26.3 to 0.26.11, after which a plain install gives the release, 0.26.0, until 0.27.0. sgit update follows the channel: a dev install moves to the newest pre-release, a release install to the newest release, --stable pins the newest release. The code is 0.26.11's, with two comment and wiring changes. Reviewed by cli.build: 0.26.12.dev0 is on PyPI; the yank had not happened when this was written. BR-4 resolved once it has.

*Source: <https://cli.sgit.ai/builds/0-26-12.html> · generated from the same content as the page, so the two cannot drift.*

---
# sgit-ai 0.26.12.dev0

```text
┌─ sgit-ai 0.26.12.dev0 ── dev build, pre-release ── 28 Oct 2026, 19:09 UTC ──────
│ tag v0.26.12 = 8eccbf43 (dev) · PyPI 0.26.12.dev0 · pip install --pre sgit-ai
│ change  dev builds are X.Y.Z.devN; a plain install gets the release
│ code    0.26.11's, plus CLI__Main and a comment in Vault__Format
│ status  0.26.3 to 0.26.11 still live on PyPI when checked: a plain install still gets 0.26.11
└──────────────────────────────────────────────────────────────────────────────────
```

## Channels now {#channels}

| You run | You get |
|---|---|
| `pip install sgit-ai` | the newest release; **today 0.26.11 until the yank is done**, then 0.26.0 |
| `pip install --pre sgit-ai` | the newest dev build, `0.26.12.dev0` |
| `pip install sgit-ai==0.26.9` | that build; a yanked version stays installable by an exact pin |
| `sgit update` | a dev install: the newest pre-release; a release install: the newest release |
| `sgit update --stable` | the newest release (`X.Y.0`), pinned so that pip goes down to it |

## Review by cli.build {#review}

**Verdict: good. BR-4 is resolved on this build, and fully once the yank is done.**
- **Checked:** the sdist of 0.26.12.dev0 differs from 0.26.11 only in `CLI__Main.py`, a comment in `Vault__Format.py` and the version. `pip index versions sgit-ai` does not list `0.26.12.dev0` (it lists 0.26.11 as the latest), and `pip install --pre` does take it.
- **Checked on PyPI, after 0.26.12.dev0 appeared:** none of 0.26.3 to 0.26.11 was yanked. A plain `pip install sgit-ai` still takes 0.26.11, so BR-4's risk is still there until the yank.
- **Not tested:** `sgit update` in all four cases (it needs an installed build to update), and the yank itself.
- **One thing to say in the release notes:** after the yank, `pip install sgit-ai` goes down to 0.26.0 for anyone on 0.26.3 to 0.26.11 who runs `pip install -U`. `sgit update --stable` is the way back to the release; a script that pins a yanked version still works.

*All builds: [the builds page](../builds/index.md).*

---

*[Site index for agents](../llms.txt) · [HTML version](https://cli.sgit.ai/builds/0-26-12.html)*