pki.sgit.ai / admin / versions
Release history
Every push to dev is a release: CI validates the site, verifies the version bump, tags the commit v{release}.{major}.{minor}, and deploys to GitHub Pages. The version is owned by admin/build/version.txt and must agree with the release commit's subject.
| Version | Date | What shipped |
|---|---|---|
| v0.1.2 | 19 Aug 2026 | Release-pipeline fix, found by the pipeline's own first run. When dev advances by a merge commit — which is how a pull request lands — HEAD is the merge and the release commit is its parent, so the tag job's "the tag must sit on HEAD" check failed and the release stopped. The job now anchors every check to the newest release commit reachable from HEAD: the version in version.txt must match the newest version in a commit subject, and the tag must sit on that commit rather than on an earlier one. The reused-version and stale-version.txt failures both still fail, which was the point of keeping the second check. Verified against the five cases, including a replay of the commit that failed. |
| v0.1.1 | 19 Aug 2026 | The site itself, refactored across from the PKI section of nhi.sgit.ai where it was staged, and promoted from three pages to a site. The failure: the 2019 keyserver attack as a dated timeline, the three abused properties mapped one-to-one onto the rules they produce, the append-only resolution, and a side-by-side of the same property safe and fatal. The rules: the four, each captioned with the property it turns around, plus a sequence diagram of revocation-as-signed-append, the attestation trade as an explicit two-way choice, and what vaults do and do not supply. Mandate: promoted from a section to its own page — identity vs. mandate, why it beats a bearer token, and the caution that a mandate constrains authority rather than behaviour. Build order: the six steps with live status, what this is not, the honest tensions, and six open questions published unresolved. Plus the documents section with the scoping brief captured verbatim and readable in-page, and the participant disclosure. |
| v0.1.0 | 19 Aug 2026 | Site scaffold, pipeline first. The validate → tag → deploy workflow adapted from SGit-AI__Website__NHI, with validation extended to pull requests and a new canonical-host check (every page must declare a canonical on the host named in CNAME — the specific mistake a refactor out of another site invites). The shared sgit.ai stylesheet carried over with this site's additions (the rules ladder, the timeline, the claim block). CNAME, robots.txt, sitemap.xml, llms.txt, the markdown twin of the front page, and this release channel. |