ungovr.providers.sgit.ai / Release history
Release history
admin/build/version.txt owns the version. bin/bump.py moves it and adds the row below. The release commit's subject repeats it, and CI refuses to tag if the two disagree — which is how a site avoids shipping two versions of itself.
| Version | Date | What changed |
|---|---|---|
| v0.1.4 | 2026-09-09 | The vault is pushed: 9 of 13 acceptance tests pass, release @2026-09-09-retrieval pinned, and the site names the commit it reports on. |
| v0.1.3 | 2026-09-09 | The vault runs live on the site, embedded through SG/Vault's own embed protocol from the published read key. |
| v0.1.2 | 2026-09-09 | The domain was pointed mid-session: 404 at v0.1.0, serving at v0.1.1. Both states recorded. |
| v0.1.1 | 2026-09-09 | The AI-law corpus, read under a key: 2,915 instruments, and a per-corpus licence that is not CC BY 4.0. Blocker B2 closed. |
| v0.1.0 | 2026-09-09 | First release. All nine contract sections; the coverage measurement and the inferred-join computation with their queries; the seven-step join; the retrieval log; the vault linked by read key. |
The pipeline
validate → tag → deploy, in that order, a failure at any stage stopping the release.
| Stage | What it does |
|---|---|
| validate | The build is reproducible against content/; the version agrees everywhere; internal links resolve; every canonical is on the host in CNAME; the key-shape scan is clean over the whole tree including docs/; every claim is cited and dated; all nine sections are present and in order |
| tag | Reads admin/build/version.txt, finds the commit whose subject carries the same version, refuses if they disagree or if the bump was not the next minor, then tags it |
| deploy | Rebuilds from content/ and publishes docs/. Never when validation failed, never from a pull request |
It also runs on pull requests, so branch work is gated before it reaches the release branch.