ci: run tap bump on the dedicated tap-writer runner #47
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!47
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/tap-writer-bump"
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-formulato target the newtap-writerrunner.Companion PR: coilyco-flight-deck/infrastructure#195 - the tap-writer runner and token provisioning this job depends on. Merge and apply that one first.
What
runs-on: tap-writer(host executor, no node) so the job is pure shell: git clone the tag, awk-rewrite the tap formula url line, git push.FORGEJO_TOKENActions secret, no token in job env or logs.Sequencing
Merge AFTER coilyco-flight-deck/infrastructure#195 is applied (the
tap-writerrunner must exist, or this job waits forever for that label). The in-repobump-formulafallback is untouched, so ward installs/upgrades keep working in the meantime.closes #46
🤖 Generated with Claude Code
Superseded by #61, which re-cuts this change against
.forgejo/workflows/release.yml. This PR targeted the pre-Forgejo-migration.github/workflows/release.yml, which was removed by #55, so it no longer applies. Closing in favor of #61.Companion infrastructure#195 is already merged (the
tap-writerrunner + token), so #61 is safe to merge now. Tracking issue #46 stays open and is closed by #61.