Public: anyone can read this; nobody can change it.
seed-release: jq-free, tag keyed to upstream.json (#263) #266
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
Task 28177's log (read from the pod — Forgejo has no run-log API) shows the true cause of every seed-release failure since birth: jq: command not found on the isolated runner image. Step 1 always worked — the github.token raw fetch and in-cluster BASE derivation are fine.
shipped merged
Sign in to join this conversation.
new above
offline
Task 28177's log (read from the pod — Forgejo has no run-log API) shows the true cause of every seed-release failure since birth:
jq: command not foundon the isolated runner image. Step 1 always worked — thegithub.tokenraw fetch and in-cluster BASE derivation are fine.idfirst). Nothing beyond curl/sed/tr/grep/tar, with a header comment holding that line.genesis/upstream.json.release— the reseed run number, the same id the seed package is versioned by. The old fallback mintedseed-r20260902045124from the manifest's seedVersion timestamp. A seed without a release id fails loudly.Proof after merge:
workflow_dispatchmust create releaseseed-r886for the current genesis (r873/r829 exist hand-made; r886 does not — a real 201-path proof, then the next reseed merge proves the push path).