From f5a8989ec703864988309acf620f0a3251dd729d Mon Sep 17 00:00:00 2001 From: TheCryptoDonkey Date: Fri, 7 Aug 2026 12:51:47 +0100 Subject: [PATCH] docs: record the 0.16.7 deploy The bridge was still running v0.16.6: 0.16.7 went to npm but never to the host. It now runs v0.16.7 built from 116798b, which is the tag plus the project page mobile fix, so the record says so rather than implying the checkout sits on a tag. --- docs/operations.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/operations.md b/docs/operations.md index 4b70385..0133d36 100644 --- a/docs/operations.md +++ b/docs/operations.md @@ -5,8 +5,10 @@ to `127.0.0.1`. Exposing a bridge is an explicit operator decision. ## Public reference bridge -The reference deployment runs release `v0.16.6` at commit -`1a603a33d3d3af4a91995437d03dfa930cc8e76f`: +The reference deployment runs release `v0.16.7` at commit +`116798bc44db356a6d279ba046fb931b8f763e27`. That commit is the `v0.16.7` tag +plus one change to `site/`, so the image is `v0.16.7` in everything the bridge +executes and the project page it serves is one commit newer: - `gopher://gopherkind.com/` - `gemini://gopherkind.com/`