bread-ecosystem package.yml fails on v* tags (pacman channel, run 312 undiagnosed) #83

New issue

Open

opened 2026-10-18 09:01:46 +08:00 by Breadway · 0 comments

Breadway commented

2026-10-18 09:01:46 +08:00

Owner

Found while verifying the bread-ecosystem v0.8.1 tag release on 2026-10-17. Pushing tag v0.8.1 triggered .forgejo/workflows/package.yml; run 312 (task id 2567) at c6442cab ended in failure. The dl.breadway.dev publish steps in release-bakery/release-bread-theme succeeded, so the bakery channel is fine, but the pacman channel did not get the package.

How found: read Breadway/bread-ecosystem's Actions tasks API and filtered head_branch=v0.8.1. The failing run is package.yml run 312 (task 2567). The job logs are not readable anonymously (actions/runs/312/jobs and actions/tasks/2567 both 404 without auth), so the specific failing step is not yet identified.

Confidence: medium that this is a real pipeline defect (the run genuinely failed and produced no package); low on the exact cause. Candidate causes, unconfirmed: missing or stale REGISTRY_TOKEN on bread-ecosystem (the release skill records that split-out repos silently lack it and every package run fails from day one), or a pacman/makepkg failure inside the archlinux:latest container (for example a stale container keyring). ECO-82 tracks only the shared-src checkout path in this same file, not this failure.

Impact: the [breadway] pacman repo does not receive bakery for v0.8.1. dl.breadway.dev is unaffected. This is the pacman channel, whose stated purpose is breadlock plus AUR republishes, so the blast radius is limited, but a red tag run that silently publishes nothing is worth closing out.

Next: retrieve run 312's logs (needs auth) and pin the failing step; fix the secret or the workflow; add a guard so a v* tag cannot silently publish nothing to the pacman channel.

Found while verifying the bread-ecosystem v0.8.1 tag release on 2026-10-17. Pushing tag v0.8.1 triggered `.forgejo/workflows/package.yml`; run 312 (task id 2567) at c6442cab ended in failure. The dl.breadway.dev publish steps in release-bakery/release-bread-theme succeeded, so the bakery channel is fine, but the pacman channel did not get the package. How found: read Breadway/bread-ecosystem's Actions tasks API and filtered head_branch=v0.8.1. The failing run is package.yml run 312 (task 2567). The job logs are not readable anonymously (actions/runs/312/jobs and actions/tasks/2567 both 404 without auth), so the specific failing step is not yet identified. Confidence: medium that this is a real pipeline defect (the run genuinely failed and produced no package); low on the exact cause. Candidate causes, unconfirmed: missing or stale REGISTRY_TOKEN on bread-ecosystem (the release skill records that split-out repos silently lack it and every package run fails from day one), or a pacman/makepkg failure inside the archlinux:latest container (for example a stale container keyring). ECO-82 tracks only the shared-`src` checkout path in this same file, not this failure. Impact: the [breadway] pacman repo does not receive bakery for v0.8.1. dl.breadway.dev is unaffected. This is the pacman channel, whose stated purpose is breadlock plus AUR republishes, so the blast radius is limited, but a red tag run that silently publishes nothing is worth closing out. Next: retrieve run 312's logs (needs auth) and pin the failing step; fix the secret or the workflow; add a guard so a v* tag cannot silently publish nothing to the pacman channel.