Repository navigation
chore: move the gateways onto fold v1.14.0 - #49
Merged
Merged
Conversation
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) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fold v1.14.0 shipped on 2026-08-15 ("interactive apps survive the trip through the gateway") and
demo.fold.runwas still serving v1.13.0 — the surface whose whole job is to be the current release, a release behind.The bump
apps/demo/Dockerfilefold:v1.13.0→v1.14.0apps/enterprise/Dockerfilefold:v1.13.0→v1.14.0apps/uptime/src/index.tsexpectVersionentries →v1.14.0apps/docs/.../conformance.mdThe pins and
expectVersionmove together because CI fails them if they drift — I ran that guard locally before pushing. The conformance receipt now points at run 31889072914, job 95022525328, resolved and confirmedconclusion: successthrough the API rather than by editing the old URL and hoping.A copy claim that had drifted
v1.14.0 also vendors a new console, and the site makes two claims about it — so I opened it in a browser instead of assuming. One was wrong:
3 of 3 connected · every route crosses auth, policy and auditCONNECTEDandLATENCYThe homepage and the walkthrough both said the map carried breaker state. Both now describe what the console actually renders. The
#/upstreams?view=maplink itself still resolves — the route survived the rewrite, which was the thing most at risk.Verified on the deployed v1.14.0
v1.14.0tools/list→ 8 tools acrosscfdocs(2),git(5),jobs(1), norun.fold/partialFailuretasks/getfrom a session that never saw it minted401still carries its RFC 9728 challengeSite and docs are deployed; both gateways are on v1.14.0.
Noted, not fixed here — a dead link inside the console
The vendored console's footer links to
https://fold.run/status/, which is 404 since #44 removed that page. That link is baked into the fold binary, so it is an upstream fix infold-run/fold, not something this repo can change. It resolves on its own if the status page comes back with fold cloud.🤖 Generated with Claude Code