ci(release): release workflow dispatch and tag push do not enqueue #51

New issue

Open

opened 2026-06-17 07:27:31 +00:00 by simon · 0 comments

simon commented

2026-06-17 07:27:31 +00:00

Owner

Summary

Release publication for merged commit 5171b93d4c was blocked because the Release workflow did not enqueue after either workflow dispatch or pushing the ct-cve-v0.9.3 tag.

Evidence

fj actions dispatch -R origin release-please.yml main -I tag_name=ct-cve-v0.9.3 -I target_ref=5171b93d4c returned success, but no new task appeared.
fj actions dispatch -R origin release-please.yml ct-cve-v0.9.3 -I tag_name=ct-cve-v0.9.3 -I target_ref=5171b93d4c also returned success, but no task appeared.
Pushed annotated tag ct-cve-v0.9.3; git ls-remote --tags origin ct-cve-v0.9.3 confirms it exists, but no tag-triggered Release workflow appeared.
fj actions tasks -R origin remained at 89 tasks with latest task #52 for CI on fix(feed): bound feed sync memory usage.

Impact

The code fix is merged and CI passed, but Docker image publication and Forgejo release creation cannot complete through the documented workflow. This leaves ct-cve-v0.9.3 tagged without a corresponding release/image until the workflow queue issue is resolved or a privileged manual Docker Hub publish is performed.

Suggested fix

Investigate Forgejo Actions workflow dispatch/tag trigger handling for .github/workflows/release-please.yml, and confirm that tag pushes matching ct-cve-v* enqueue the Release workflow. Add a small documented fallback or admin runbook if dispatch remains unreliable.

## Summary Release publication for merged commit 5171b93d4c was blocked because the Release workflow did not enqueue after either workflow dispatch or pushing the ct-cve-v0.9.3 tag. ## Evidence - `fj actions dispatch -R origin release-please.yml main -I tag_name=ct-cve-v0.9.3 -I target_ref=5171b93d4c` returned success, but no new task appeared. - `fj actions dispatch -R origin release-please.yml ct-cve-v0.9.3 -I tag_name=ct-cve-v0.9.3 -I target_ref=5171b93d4c` also returned success, but no task appeared. - Pushed annotated tag `ct-cve-v0.9.3`; `git ls-remote --tags origin ct-cve-v0.9.3` confirms it exists, but no tag-triggered Release workflow appeared. - `fj actions tasks -R origin` remained at 89 tasks with latest task #52 for CI on `fix(feed): bound feed sync memory usage`. ## Impact The code fix is merged and CI passed, but Docker image publication and Forgejo release creation cannot complete through the documented workflow. This leaves `ct-cve-v0.9.3` tagged without a corresponding release/image until the workflow queue issue is resolved or a privileged manual Docker Hub publish is performed. ## Suggested fix Investigate Forgejo Actions workflow dispatch/tag trigger handling for `.github/workflows/release-please.yml`, and confirm that tag pushes matching `ct-cve-v*` enqueue the `Release` workflow. Add a small documented fallback or admin runbook if dispatch remains unreliable.