From 3f578aed4d7a0699d26c673da22522e1b0d28262 Mon Sep 17 00:00:00 2001 From: Blake Bauman Date: Tue, 25 Aug 2026 20:25:10 -0700 Subject: [PATCH] chore: move the gateways onto fold v1.14.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit v1.14.0 shipped on 2026-08-15 and the demo was still serving v1.13.0 — the surface whose whole job is to be the current release, a release behind. Both Dockerfiles and both expectVersion entries move together, which is what the CI guard exists to enforce, and the conformance receipt repoints at the v1.14.0 release run (run 31889072914, job 95022525328 — confirmed green via the API rather than by editing the URL and hoping). v1.14.0 also vendors a new console, so the two console claims on the site were re-checked against it in a browser rather than assumed. One had drifted: the map view now labels each route with that upstream's live latency and summarises health as "3 of 3 connected", while breaker state lives in the upstreams table as its own column. The homepage and the walkthrough said the map carried breaker state. Both now say what the console actually renders. Verified on the deployed v1.14.0: both gateways report v1.14.0, the federation returns 8 tools across three namespaces with no partialFailure, a minted task still resolves from a session that never saw it minted, the enterprise 401 still carries its RFC 9728 challenge, and the map view at #/upstreams?view=map still loads. Co-Authored-By: Claude Opus 5 (1M context) --- apps/demo/Dockerfile | 2 +- apps/docs/src/content/docs/conformance.md | 2 +- apps/docs/src/content/docs/try-the-demo.md | 2 +- apps/enterprise/Dockerfile | 2 +- apps/site/src/pages/index.astro | 9 +++++---- apps/uptime/src/index.ts | 4 ++-- 6 files changed, 11 insertions(+), 10 deletions(-) diff --git a/apps/demo/Dockerfile b/apps/demo/Dockerfile index 6072237..739df58 100644 --- a/apps/demo/Dockerfile +++ b/apps/demo/Dockerfile @@ -3,7 +3,7 @@ # image until `pnpm --filter @fold-run/demo run deploy` runs. Update # expectVersion in apps/uptime/src/index.ts in the same commit — CI enforces # it, and the monitor then catches a pin that shipped without a deploy. -FROM ghcr.io/fold-run/fold:v1.13.0 +FROM ghcr.io/fold-run/fold:v1.14.0 # Distroless ENTRYPOINT is ["/fold"]; bind beyond loopback for the container # network. Config arrives via FOLD_CONFIG (set by the Container class). CMD ["--host", "0.0.0.0", "--port", "8080", "--log-format", "json"] diff --git a/apps/docs/src/content/docs/conformance.md b/apps/docs/src/content/docs/conformance.md index 8bfb120..b76994e 100644 --- a/apps/docs/src/content/docs/conformance.md +++ b/apps/docs/src/content/docs/conformance.md @@ -20,7 +20,7 @@ servers back to the originating client. **The receipt is one click away**, because a conformance claim you have to take on faith isn't one: the -[`conformance` job from the v1.13.0 release run](https://github.com/fold-run/fold/actions/runs/31833840044/job/94875553255), +[`conformance` job from the v1.14.0 release run](https://github.com/fold-run/fold/actions/runs/31889072914/job/95022525328), and [every green run on `main`](https://github.com/fold-run/fold/actions/workflows/ci.yml?query=branch%3Amain+is%3Asuccess). diff --git a/apps/docs/src/content/docs/try-the-demo.md b/apps/docs/src/content/docs/try-the-demo.md index 6a52b0f..f1b4651 100644 --- a/apps/docs/src/content/docs/try-the-demo.md +++ b/apps/docs/src/content/docs/try-the-demo.md @@ -95,7 +95,7 @@ GitMCP speaks the 2025-era session handshake. fold — built on the official Go ## 5. Watch it in the console -Open **[demo.fold.run/console](https://demo.fold.run/console/)** — the read-only [fold console](/console/), enabled in the demo's config. The dashboard shows the three upstreams, their breaker state, and the deployment facts live, and **[the map view](https://demo.fold.run/console/#/upstreams?view=map)** draws the federation itself: one gateway node fanning out to cfdocs, git, and jobs, each route carrying that upstream's current breaker state. It's generated from `/api/federation`, so it's this demo's real topology, not a picture of one. The test console is a plain MCP client against the same `/mcp` endpoint you've been curling, governed and audited like any other caller. +Open **[demo.fold.run/console](https://demo.fold.run/console/)** — the read-only [fold console](/console/), enabled in the demo's config. The upstreams table shows a row per upstream — namespace, source, auth, connected, breaker, latency — and **[the map view](https://demo.fold.run/console/#/upstreams?view=map)** draws the federation itself: one gateway node fanning out to cfdocs, git, and jobs, each route labelled with the latency that upstream is answering in, over a footer reading `3 of 3 connected · every route crosses auth, policy and audit`. It's generated from `/api/federation`, so it's this demo's real topology, not a picture of one. The test console is a plain MCP client against the same `/mcp` endpoint you've been curling, governed and audited like any other caller. ## The same federation, governed diff --git a/apps/enterprise/Dockerfile b/apps/enterprise/Dockerfile index 9402d6c..ed7d645 100644 --- a/apps/enterprise/Dockerfile +++ b/apps/enterprise/Dockerfile @@ -4,7 +4,7 @@ # step with apps/demo/Dockerfile, and update expectVersion in # apps/uptime/src/index.ts in the same commit — CI enforces it, and the monitor # then catches a pin that shipped without a deploy. -FROM ghcr.io/fold-run/fold:v1.13.0 +FROM ghcr.io/fold-run/fold:v1.14.0 # Distroless ENTRYPOINT is ["/fold"]; bind beyond loopback for the container # network. Config arrives via FOLD_CONFIG (set by the Container class). CMD ["--host", "0.0.0.0", "--port", "8080", "--log-format", "json"] diff --git a/apps/site/src/pages/index.astro b/apps/site/src/pages/index.astro index 6e4150d..491b2d1 100644 --- a/apps/site/src/pages/index.astro +++ b/apps/site/src/pages/index.astro @@ -210,11 +210,12 @@ const jsonld = {

The console ships inside the binary and needs no client. Open it and you are reading the - running federation: live latency and breaker state per upstream, the policy in effect, the - rate limit. Its test console calls the same endpoint everything else does. The topology - at the top of this page is drawn by hand; the console draws its own from the federation it is serving. + > from the federation it is serving, each route labelled with the latency it is answering + in.

diff --git a/apps/uptime/src/index.ts b/apps/uptime/src/index.ts index c4f81a8..392bebc 100644 --- a/apps/uptime/src/index.ts +++ b/apps/uptime/src/index.ts @@ -85,7 +85,7 @@ const TARGETS: Target[] = [ // Real JSON-RPC round trips (initialize), not just a 200 — we monitor // the protocol, not the port. Checking the tasks upstream directly also // separates "gateway down" from "upstream down" when demo alerts fire. - { id: 'demo', kind: 'mcp-init', url: 'https://demo.fold.run/mcp', expectVersion: 'v1.13.0' }, + { id: 'demo', kind: 'mcp-init', url: 'https://demo.fold.run/mcp', expectVersion: 'v1.14.0' }, { id: 'demo-tasks', kind: 'mcp-init', url: 'https://tasks.fold.run/mcp' }, // The governed gateway. Its correct answer to an anonymous initialize is a // 401, so it needs the guarded check rather than the one the demo uses. @@ -94,7 +94,7 @@ const TARGETS: Target[] = [ kind: 'mcp-guarded', url: 'https://enterprise.fold.run/mcp', versionUrl: 'https://enterprise.fold.run/health', - expectVersion: 'v1.13.0', + expectVersion: 'v1.14.0', }, // fold cloud — the half of the estate that has customers. Published: with no