Public: anyone can read this; nobody can change it.

seed-release: jq-free, tag keyed to upstream.json (#263) #266

Merged opened this view on origin

Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.

Merged

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.

Notes

shipped merged

opened this view on origin

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.

  • jq-free: JSON built with printf from controlled fields; release id read via tr/sed (Go marshals struct order — id first). Nothing beyond curl/sed/tr/grep/tar, with a header comment holding that line.
  • Tag from genesis/upstream.json .release — the reseed run number, the same id the seed package is versioned by. The old fallback minted seed-r20260902045124 from the manifest's seedVersion timestamp. A seed without a release id fails loudly.

Proof after merge: workflow_dispatch must create release seed-r886 for 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).

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs