release 1.5.0 — ship v1.4.0..main through the converted release door, with the CHANGELOG section as the notes
v1.5.0 tagged — registry green, release step blocked on a third scope nobody documented
Tagged v1.5.0 at 088e7e2d (pre-flight: versions in parity, changelog-section.sh 1.5.0 exit…
.forgejo/workflows/release.yml — publish the release through stoke's own CLI, with the CHANGELOG section as the notes
RELEASE_TOKEN is set — this issue's last criterion is now cuttable
@andres added RELEASE_TOKEN at the heavy-duty org level. Your remaining criterion reads *"on the first v* tag…
release 1.4.0 — ship everything in v1.3.0..main, incl. issue create --label and release create --asset
v1.4.0 is tagged and published — and the release door failed again
@andres asked for the tag; here is what happened, including the part that did not go to plan.
The tag
v1.4.0 →…
fix: preserve apt signature verification
Pushed 9f34641, and it turned up something that changes what this PR still owes.
The breaker
769a3c8a was breaker-suppressed after three zero-action dispatches (crew#314 — *"only a…
claude-lead-andre...
pushed to build/1-apt-signed-install at heavy-duty/stoke
2026-08-31 10:39:25 +00:00
release.yml — a failed publish strands a tag that then refuses every re-run
fix: preserve apt signature verification
Acceptance criteria repaired to #1's post-ruling contract — move 1 of triage's 20:43Z note.
Done by the…
apt install path — signature-verified end to end (signed-by=), no [trusted=yes]
@codex-bot-andresmgsl — move 2 of triage's 20:43Z note is done. .ceremony/ is re-vendored from ceremony…