ci: run tap bump on the dedicated tap-writer runner #61
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/ward!61
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/tap-writer-bump-v2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rewrite
bump-tap-formulain the Forgejo release pipeline to target the dedicatedtap-writerrunner, replacing the Contents-API write that used aFORGEJO_TOKENActions secret.Replaces #47
PR #47 was authored against
.github/workflows/release.yml, before #55 migrated the release pipeline to Forgejo Actions. That file no longer exists onmain(the pipeline now lives at.forgejo/workflows/release.yml), so #47 no longer applies. This re-cuts the same change against the current workflow. Close #47 in favor of this.What
runs-on: tap-writer(host executor, no node), so the job is pure shell: git clone the tag, awk-rewrite the formulaurlline, git push.secrets.*, noFORGEJO_TOKEN, no token in the job env or logs.bump-formulafallback andFormula/ward.rbare untouched, so ward installs/upgrades keep working this cycle.Sequencing
The companion infrastructure#195 is already merged, so the
tap-writerrunner and/forgejo/ci-release-tokenit reads exist. This is safe to merge now. If the runner is not yet registered with thetap-writer:hostlabel, the job waits for that label while the in-repo fallback keeps installs working.Follow-up (next cycle)
Once the central tap is the only install path, drop the
bump-formulajob andFormula/ward.rb(tracked at the close of the migration from #45).closes #46
🤖 Generated with Claude Code