ci(release): investigate missing release workflow runs for tags and dispatch #49

New issue

Open

opened 2026-06-14 14:50:50 +00:00 by simon · 0 comments

simon commented

2026-06-14 14:50:50 +00:00

Owner

Summary

During the CT-CVE 0.9.2 release, neither creating/pushing tag ct-cve-v0.9.2 nor manually dispatching .github/workflows/release-please.yml queued a visible Publish Forgejo release task.

Evidence

fj tag create ct-cve-v0.9.2 -B main created the tag but no release task appeared in fj actions tasks.
Replacing the tag with a normal Git-pushed annotated tag also did not queue the tag-triggered release workflow.
fj actions dispatch release-please.yml main -I tag_name=ct-cve-v0.9.2 -I target_ref=c4331f9... returned success but did not create a visible task.
Dispatching by display name Release returned a Forgejo 500.
Previous releases, for example task #42 for ct-cve-v0.9.1, show the Publish Forgejo release job working in the past.

Impact

The 0.9.2 image and release had to be published manually with Docker Buildx plus fj release asset commands. This creates avoidable release risk and can leave fixes unpublished if not noticed.

Suggested next steps

Check Forgejo Actions event handling for tag pushes and workflow dispatches on this repo, including whether workflow dispatch runs are hidden from fj actions tasks, whether tag push events are disabled, or whether the runner/controller rejected the queued job before task creation.

## Summary During the CT-CVE 0.9.2 release, neither creating/pushing tag `ct-cve-v0.9.2` nor manually dispatching `.github/workflows/release-please.yml` queued a visible `Publish Forgejo release` task. ## Evidence - `fj tag create ct-cve-v0.9.2 -B main` created the tag but no release task appeared in `fj actions tasks`. - Replacing the tag with a normal Git-pushed annotated tag also did not queue the tag-triggered release workflow. - `fj actions dispatch release-please.yml main -I tag_name=ct-cve-v0.9.2 -I target_ref=c4331f9...` returned success but did not create a visible task. - Dispatching by display name `Release` returned a Forgejo 500. - Previous releases, for example task #42 for `ct-cve-v0.9.1`, show the `Publish Forgejo release` job working in the past. ## Impact The 0.9.2 image and release had to be published manually with Docker Buildx plus `fj release` asset commands. This creates avoidable release risk and can leave fixes unpublished if not noticed. ## Suggested next steps Check Forgejo Actions event handling for tag pushes and workflow dispatches on this repo, including whether workflow dispatch runs are hidden from `fj actions tasks`, whether tag push events are disabled, or whether the runner/controller rejected the queued job before task creation.