Forge-to-forge compatibility, measured (#8900)

Written by scripts/forge-compat-lab.sh; run it on any docker host to get this table again. It starts three real forges in containers on a private network, behind TLS with a throwaway authority, seeds them, and drives them with HTTP and git. No live forge is touched.

What "old" is. The real forge at forge-apps.benjivers.com reports 0.5.29, commit 2d910c08. That commit and that tag are in no repository this lab can read. The oldest honest stand-in is trunk ce7846af, the last commit before /api/v1/version: its contract matches the live forge's published OpenAPI on 325 of 332 routes, with the same absences (/api/v1/version, /api/v1/user/repos) and the same OAuth metadata. The other 7 are routes only the live forge has (admin users, check secrets, org teams); none is one an origin calls. So this is a reconstruction of 0.5.29, not 0.5.29.

The refused token. A forge before /api/v1/version reads Bearer and Basic only (src/http/server.ts at ce7846af). This forge sent Authorization: token …, the Gitea scheme, so a good token answered 401 and read as "That token was refused by the origin". ForgeProvider now sends Bearer always. Scopes were not the cause: ro connects.

Absent, and what this cannot show. absent is a thing not built, or not checkable here, said plainly.

The public group was also read from the real forge-apps.benjivers.com, anonymously, through the provider (scripts/forge-compat-lab/live-public.ts): 16 public repositories, none yours or shared, as an account owning nothing there should see.

Result

DirectionAreaCheckResultSeen
forge-old1 discoveryhealth names version and commitpassversion 0.5.29; /api/v1/version 404; /user/repos 404
forge-old2 token schemeGET /user with Bearerpass200 as ann
forge-old2 token schemeGET /user with tokenpass401: an old forge reads Bearer and Basic only, so a forge must send Bearer
forge-old2 token schemeGET /user with Basicpass200 as ann
forge-old3 oauth endpointsregister, consent, token, refresh rotates, reused code and refresh refusedpasslifetime day; Bearer ro
forge-old3 oauth endpointsredirect-URI mismatch refused before any codepass
forge-oldseedissues, a pull, labels, comments, a tag, by two people, and a big treepass2436 files
forge-newseedissues, a pull, labels, comments, a tag, by two people, and a big treepass2436 files
forge-new2seedissues, a pull, labels, comments, a tag, by two people, and a big treepass2436 files
forge-new reads forge-old1 discoveryan address that is no forge is refused in wordspassunreachable: that host could not be reached
forge-new reads forge-old2 connect by tokena made-up token is refusedpass
forge-new reads forge-old2 connect by tokenan administrator connects as themselves, a person's own accountpasslogin boss
forge-new reads forge-old2 connect by tokenan everyday ro token connectspasslogin ann, software forge
forge-new reads forge-old1 discoverythe address is stored as a forgepasskind gitea
forge-new reads forge-old4 listown repositories across pages, private ones included, nobody else'spass135 in 1 pages
forge-new reads forge-old5 bringa public repository: history, branches, tags identicalpass3 refs
forge-new reads forge-old5 bringissues and comments, authors keptpass#1, 1 comment
forge-new reads forge-old5 bringpullspass#2 open
forge-new reads forge-old5 bringlabelspass
forge-new reads forge-old5 bringa label stays on its issuepass
forge-new reads forge-old5 bringa private repository, with the credentialpass
forge-new reads forge-old5 bringa big repository, whole treepass1 s, main 32d7ce0a
forge-new reads forge-old6 synca commit there arrives here with a syncpass
forge-new reads forge-old6 syncan issue opened there appears here (webhook, else sync)passby sync (no webhook seen)
forge-new reads forge-old6 synca pull opened there appears herepassby sync
forge-new reads forge-old6 syncwith a ro token, writing here is refused in words, nothing keptpass409 origin_refused: the origin refused this change; nothing was changed here either
forge-new reads forge-old7 failurea revoked token: said plainly, marked to reconnect, and a new token repairs itpassfailed: the origin has no such repository, or this account cannot see it; needsReauth
forge-new reads forge-old7 failureconnecting a new token after that workspassrw
forge-new reads forge-old6 syncwith a rw token, a comment here lands there, under the same issuepass
forge-new reads forge-old6 syncwith a rw token, an issue opened here is opened therepass
forge-new reads forge-old6 syncwebhook: a rw or signed-in token cannot register one (a hook needs admin scope there)absentno hook registered: the sweep is the only way back without admin scope
forge-new reads forge-old6 syncwebhook with an admin-scope token: an issue opened there arrives without a syncabsentthe hook is registered; its delivery is refused by the source's SSRF guard, as it should be for this lab's private network. Not verified end to end.
forge-new reads forge-old6 synca git push to a fresh mirror lands on the origin, and a pull opened here opens therepass
forge-new reads forge-old6 synca git push to a mirror whose origin was disconnected and connected again still lands therepass
forge-new reads forge-old7 failurea repository this account cannot read does not come acrosspassjob failed: the origin has no such repository, or this account cannot see it
forge-new reads forge-old7 failurea token that lost access: the repository went private there, a sync says so and keeps the copypasssync 200 the origin has no such thing; lastError the origin has no such thing; needsReauth false
forge-new reads forge-old7 failurethe origin down in the middle of a bring: fails in words, then succeedspassjob failed: the origin could not be reached
forge-new reads forge-old7 failurethe origin killed while a big bring runs: fails in words, then succeedspassfirst: failed Fetching from the origin failed: Error: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second ar
forge-new reads forge-old4 groupsowning nothing: yours is empty, the organization's repository is shared, others' are publicpass100 public on the first page
forge-new reads forge-old4 groupspublic pages past the first, and search narrows itpass121 in 2 pages
forge-new reads forge-old4 groupsthe page labels all threepass
forge-new reads forge-old6 work withsomeone else's public repository comes across for someone with read onlypass
forge-new reads forge-old6 work withro: sending work back is refused in words, nothing therepassthe origin refused: this connection cannot write there, and a fork there takes a token that can write (rw). Nothing was changed. Connect again with one, or ask
forge-new reads forge-old6 work withrw: sending work back forks it there and opens a pull, authored by thempass#1 by dee, from their fork
forge-new reads forge-old6 followa followed source: a new commit there opens one pull herepass
forge-new reads forge-old3 sign-inthrough the flow page, the approve form and back, connected as forgepassauthKind oauth, expires 2026-11-05T18:00:41.377Z
forge-new reads forge-old4 listwith the signed-in tokenpass135 repositories
forge-new reads forge-old5 bringa bring with the signed-in tokenpass
forge-new reads forge-old3 sign-inan expiring token refreshes itself before expirypassexpiry moved to 2026-11-05T18:00:42.704Z
forge-new reads forge-old7 failurea wrong state at the callback connects nothing and says sopassThat authorization could not be matched to a connect you started here. Start again.
forge-new reads forge-old7 failurea code used twice at the callback connects nothing the second timepassfirst ?connected=1, second ?error=state
forge-new reads forge-old7 failurethe wrong verifier and a mismatched redirect at the originpass
forge-new reads forge-old7 failurethe origin down at sign-in says so in words, then signs inpass422: That address could not be reached, or no forge answered there.
forge-old reads forge-new1 discoveryan address that is no forge is refused in wordspassunreachable: that host could not be reached
forge-old reads forge-new2 connect by tokena made-up token is refusedpass
forge-old reads forge-new2 connect by tokenan administrator connects as themselves, a person's own accountabsentbad_token: an old forge reads another forge as Gitea and finds no login
forge-old reads forge-new2 connect by tokenan everyday ro token connectsabsentbad_token: an old forge reads another forge as Gitea and finds no login
forge-old reads forge-new1 discoverythe address is stored as a forgeabsentnot connected, so nothing stored
forge-old reads forge-new3 sign-inthe old forge offers no sign-in to another forgeabsentlanded /settings/origins; (no message on the page)
forge-old reads forge-new4-7list, bring, sync, failureabsenta forge older than forge-to-forge cannot connect another forge at all; upgrade it. Nothing here can fix an old build.
forge-new2 reads forge-new1 discoveryan address that is no forge is refused in wordspassunreachable: that host could not be reached
forge-new2 reads forge-new2 connect by tokena made-up token is refusedpass
forge-new2 reads forge-new2 connect by tokenan administrator connects as themselves, a person's own accountpasslogin boss
forge-new2 reads forge-new2 connect by tokenan everyday ro token connectspasslogin ann, software forge
forge-new2 reads forge-new1 discoverythe address is stored as a forgepasskind gitea
forge-new2 reads forge-new4 listown repositories across pages, private ones included, nobody else'spass143 in 1 pages
forge-new2 reads forge-new5 bringa public repository: history, branches, tags identicalpass3 refs
forge-new2 reads forge-new5 bringissues and comments, authors keptpass#1, 1 comment
forge-new2 reads forge-new5 bringpullspass#2 open
forge-new2 reads forge-new5 bringlabelspass
forge-new2 reads forge-new5 bringa label stays on its issuepass
forge-new2 reads forge-new5 bringa private repository, with the credentialpass
forge-new2 reads forge-new5 bringa big repository, whole treepass1 s, main c50dfe6f
forge-new2 reads forge-new6 synca commit there arrives here with a syncpass
forge-new2 reads forge-new6 syncan issue opened there appears here (webhook, else sync)passby sync (no webhook seen)
forge-new2 reads forge-new6 synca pull opened there appears herepassby sync
forge-new2 reads forge-new6 syncwith a ro token, writing here is refused in words, nothing keptpass409 origin_refused: the origin refused this change; nothing was changed here either
forge-new2 reads forge-new7 failurea revoked token: said plainly, marked to reconnect, and a new token repairs itpassfailed: the origin has no such repository, or this account cannot see it; needsReauth
forge-new2 reads forge-new7 failureconnecting a new token after that workspassrw
forge-new2 reads forge-new6 syncwith a rw token, a comment here lands there, under the same issuepass
forge-new2 reads forge-new6 syncwith a rw token, an issue opened here is opened therepass
forge-new2 reads forge-new6 syncwebhook: a rw or signed-in token cannot register one (a hook needs admin scope there)absentno hook registered: the sweep is the only way back without admin scope
forge-new2 reads forge-new6 syncwebhook with an admin-scope token: an issue opened there arrives without a syncabsentthe hook is registered; its delivery is refused by the source's SSRF guard, as it should be for this lab's private network. Not verified end to end.
forge-new2 reads forge-new6 synca git push to a fresh mirror lands on the origin, and a pull opened here opens therepass
forge-new2 reads forge-new6 synca git push to a mirror whose origin was disconnected and connected again still lands therepass
forge-new2 reads forge-new7 failurea repository this account cannot read does not come acrosspassjob failed: the origin has no such repository, or this account cannot see it
forge-new2 reads forge-new7 failurea token that lost access: the repository went private there, a sync says so and keeps the copypasssync 200 the origin has no such thing; lastError the origin has no such thing; needsReauth false
forge-new2 reads forge-new7 failurethe origin down in the middle of a bring: fails in words, then succeedspassjob failed: the origin could not be reached
forge-new2 reads forge-new7 failurethe origin killed while a big bring runs: fails in words, then succeedspassfirst: failed Fetching from the origin failed: Error: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second ar
forge-new2 reads forge-new4 groupsowning nothing: yours is empty, the organization's repository is shared, others' are publicpass98 public on the first page
forge-new2 reads forge-new4 groupspublic pages past the first, and search narrows itpass131 in 2 pages
forge-new2 reads forge-new4 groupsthe page labels all threepass
forge-new2 reads forge-new6 work withsomeone else's public repository comes across for someone with read onlypass
forge-new2 reads forge-new6 work withro: sending work back is refused in words, nothing therepassthe origin refused: this connection cannot write there, and a fork there takes a token that can write (rw). Nothing was changed. Connect again with one, or ask
forge-new2 reads forge-new6 work withrw: sending work back forks it there and opens a pull, authored by thempass#1 by dee, from their fork
forge-new2 reads forge-new6 followa followed source: a new commit there opens one pull herepass
forge-new2 reads forge-new3 sign-inthrough the flow page, the approve form and back, connected as forgepassauthKind oauth, expires 2026-11-05T18:01:59.681Z
forge-new2 reads forge-new4 listwith the signed-in tokenpass143 repositories
forge-new2 reads forge-new5 bringa bring with the signed-in tokenpass
forge-new2 reads forge-new3 sign-inan expiring token refreshes itself before expirypassexpiry moved to 2026-11-05T18:02:01.068Z
forge-new2 reads forge-new7 failurea wrong state at the callback connects nothing and says sopassThat authorization could not be matched to a connect you started here. Start again.
forge-new2 reads forge-new7 failurea code used twice at the callback connects nothing the second timepassfirst ?connected=1, second ?error=state
forge-new2 reads forge-new7 failurethe wrong verifier and a mismatched redirect at the originpass
forge-new2 reads forge-new7 failurethe origin down at sign-in says so in words, then signs inpass422: That address could not be reached, or no forge answered there.
↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs