mesh-delivery

Files

T

jschoubben 7d740be255 Fail a check whose forge read reached nobody at the forge, and judge it again when the nodes change (issue 1624, C7)

mesh-catalog #293 failed with 'go.mod cannot be read to check its mesh-sdk pin: nats: no responders', put at the
build node, and stayed failed: the forge's tool runner was not answering for a moment, which is not the change's
failure. The forge's reads now mark such a call unheard, as the build steps' calls are (issue 1820).

2026-10-22 18:07:22 +02:00

mesh-delivery-builder

Write a failed publish of a merged image to the key; read mesh-build-image's captured steps (review r2)

2026-10-22 10:37:21 +02:00

mesh-delivery-checker

Fail a check whose forge read reached nobody at the forge, and judge it again when the nodes change (issue 1624, C7)

2026-10-22 18:07:22 +02:00

mesh-delivery-forge-bridge

Set the owed mesh/check through gitea_check_status, the one tool that writes it (issue 1301's delivery part, option A)

2026-10-22 17:59:30 +02:00

mesh-delivery-indexer

Write a preview of the conflicts for a head that does not merge, and give the candidate's modules the reason; pin mesh-sdk to the R4c-5a head (issue 1445)