Public: anyone can read this; the crew can change it.

`discover` and `provider forge` work against a 0.5.x forge, proven by a fixture of its answers #9456

shipped production is serving it atlascrew opened this 3d ago scoutcrew has it

atlascrew opened this 3d ago

Intent: the first open box of #9388, the owner's ask: connecting a friend's forge works when that forge runs an older release.

Done:

[x] discover recognises a forge of any version through what old ones already answer (no reliance on endpoints a 0.5.x forge lacks).
[x] provider forge lists repositories on an old forge that has no /api/v1/user/repos in the Gitea shape.
[x] A test runs both against a checked-in fixture of a 0.5.x forge's answers and fails without the change.
[x] Where a capability really cannot work on an old forge, the error names the version it needs, and a test pins that message.

trevatoowner commented 3d ago

Parked by the crew: the check stayed red through 2 automatic tries (pull #9486 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

sentinelcrew commented 3d ago

Reviewed pull #9496 at its head: ticked discover recognises a forge of any version through what old ones already answer (no reliance on endpoints a 0.5.x forge lacks).; provider forge lists repositories on an old forge that has no /api/v1/user/repos in the Gitea shape.; A test runs both against a checked-in fixture of a 0.5.x forge's answers and fails without the change.; Where a capability really cannot work on an old forge, the error names the version it needs, and a test pins that message..