coilyco-bridge/coily

Fork 0

release automation: bump-formula fails every run and push did not trigger a new run #137

New issue

Closed

opened 2026-05-28 07:32:46 +00:00 by coilysiren · 3 comments

coilysiren commented

2026-05-28 07:32:46 +00:00

Owner

Problem Two release-automation issues observed while shipping the cli-guard v0.1.0 bump (#135).

1. bump-formula fails on every recent release. actions task list shows bump-formula in the failure state for run#42, run#43, and run#45, while release and windows-assets succeed in the same runs. Net effect: tags + releases get cut, but Formula/coily.rb is not bumped, so the brew install path lags the actual release. This is the likely reason a kai-server checkout was pinned at v2.29.1 while v2.43.0 was current. Could not read the job log to root-cause: coily ops forgejo actions task logs does an in-pod read over SSH to kai-server, which failed from this session with ssh: no authentication method available.

2. Push to main did not visibly trigger a run. Commit c076c0a (chore(deps): bump cli-guard to v0.1.0) is confirmed at the tip of forgejo main, but no new Actions run appeared within ~2 min of the push (latest remained run#45, from the earlier workflow-editing commit feb7a45e). Either the docker runner was offline/cold, or the push event did not enqueue a run. Needs a check of runner health and whether pushes since feb7a45e have been triggering at all.

Both block the goal of brew upgrade coily pulling the lockdown newline fix: even a successful tag won't reach the formula while bump-formula fails.

**Problem** Two release-automation issues observed while shipping the cli-guard v0.1.0 bump (#135). **1. bump-formula fails on every recent release.** `actions task list` shows `bump-formula` in the `failure` state for run#42, run#43, and run#45, while `release` and `windows-assets` succeed in the same runs. Net effect: tags + releases get cut, but `Formula/coily.rb` is not bumped, so the brew install path lags the actual release. This is the likely reason a kai-server checkout was pinned at v2.29.1 while v2.43.0 was current. Could not read the job log to root-cause: `coily ops forgejo actions task logs` does an in-pod read over SSH to kai-server, which failed from this session with `ssh: no authentication method available`. **2. Push to main did not visibly trigger a run.** Commit c076c0a (`chore(deps): bump cli-guard to v0.1.0`) is confirmed at the tip of forgejo `main`, but no new Actions run appeared within ~2 min of the push (latest remained run#45, from the earlier workflow-editing commit feb7a45e). Either the docker runner was offline/cold, or the push event did not enqueue a run. Needs a check of runner health and whether pushes since feb7a45e have been triggering at all. Both block the goal of `brew upgrade coily` pulling the lockdown newline fix: even a successful tag won't reach the formula while bump-formula fails.

coilysiren commented

2026-05-28 08:08:03 +00:00

Author

Owner

Root-causing the bump-formula failure here was blocked because coily ops forgejo actions task logs reads the task log in-pod over SSH to kai-server, which fails in
any session without an SSH key loaded. Converting all forgejo verbs to HTTPS is
tracked in #139, and is a prerequisite for diagnosing this from a keyless session.

Root-causing the bump-formula failure here was blocked because `coily ops forgejo actions task logs` reads the task log in-pod over SSH to kai-server, which fails in any session without an SSH key loaded. Converting all forgejo verbs to HTTPS is tracked in #139, and is a prerequisite for diagnosing this from a keyless session.

coilysiren commented

2026-05-28 08:22:45 +00:00

Author

Owner

Root cause confirmed: HTTP 401 on the formula bump PUT

Pulled the bump-formula log for run#45 (task 130) over HTTPS while building the
#139 fix. The failing step is the coilysiren/agentic-os/actions/bump-formula@main
action, and the error is:

::error::forgejo formula bump failed: HTTP 401
⚙️ [runner]: exitcode '1': failure

So the job runs fine up to the Contents API PUT, which comes back 401
Unauthorized. The action authenticates that PUT with secrets.FORGEJO_PAT
(see .forgejo/workflows/release.yml job bump-formula, input forgejo_token).
A 401 means that secret is unset, empty, or lacks write:repository scope on the
forgejo instance.

Fix

Set / re-scope the FORGEJO_PAT repo (or org) secret on forgejo with Contents
write permission, then re-run a release. No code change in this repo is needed.

This is independent of #139 (that issue is about coily reading these logs over
HTTPS instead of SSH, which is how this log was retrieved).

## Root cause confirmed: HTTP 401 on the formula bump PUT Pulled the bump-formula log for run#45 (task 130) over HTTPS while building the #139 fix. The failing step is the `coilysiren/agentic-os/actions/bump-formula@main` action, and the error is: ``` ::error::forgejo formula bump failed: HTTP 401 ⚙️ [runner]: exitcode '1': failure ``` So the job runs fine up to the Contents API PUT, which comes back **401 Unauthorized**. The action authenticates that PUT with `secrets.FORGEJO_PAT` (see `.forgejo/workflows/release.yml` job `bump-formula`, input `forgejo_token`). A 401 means that secret is unset, empty, or lacks `write:repository` scope on the forgejo instance. ### Fix Set / re-scope the `FORGEJO_PAT` repo (or org) secret on forgejo with Contents write permission, then re-run a release. No code change in this repo is needed. This is independent of #139 (that issue is about coily reading these logs over HTTPS instead of SSH, which is how this log was retrieved).

coilysiren commented

2026-05-30 05:43:12 +00:00

Author

Owner

Merged into #103 in the 2026-05-29 backlog burn-down. Duplicate bump-formula fails every release Reopen if it should stand alone.

coilysiren closed this issue

2026-05-30 05:43:13 +00:00

coilysiren added the

label

2026-05-31 01:52:37 +00:00

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

coilyco-bridge/coily#137

No description provided.

Rows
Columns