publish_release: CI retry on the bump PR cannot clear failed statuses #8

Closed
opened 2026-11-11 00:18:45 +01:00 by robin.wieske · 1 comment
Owner

Context

publish_release.yaml in Aevana, kima/portal and slight-exposure retries a failed CI run on the version-bump PR by dispatching ci.yaml on the same branch. Commit status contexts include the trigger (for example CI / test (push)), so a dispatched run adds new (workflow_dispatch) statuses next to the failed (push) ones. The combined status of the commit stays failure, so the retry cannot turn the bump PR green. The flaw predates the rollout.

Kardeema (#2218) works around it: a retry closes the bump PR and recreates it as a new commit, so CI runs fresh on a commit without failed statuses.

Plan: https://forgejo.entwirr.me/Wi3eDigital/laravel-deploy-actions/src/branch/main/docs/plan.md

Tasks

  • Confirm on one repo (for example Aevana) that a dispatched CI run leaves the failed (push) statuses in place and the combined state stays failure.
  • Port Kardeema's approach (Kardeema/kardeema publish_release.yaml, PR #2218) to Aevana, kima/portal and slight-exposure, or move the bump step into a shared action.
  • Also find the bump PR by branch name (head filter), not by scanning the first page of open PRs.

Acceptance criteria

  • A flaky CI failure on the bump PR is retried and can end green in every repo using the shared publish flow.
## Context `publish_release.yaml` in Aevana, kima/portal and slight-exposure retries a failed CI run on the version-bump PR by dispatching `ci.yaml` on the same branch. Commit status contexts include the trigger (for example `CI / test (push)`), so a dispatched run adds new `(workflow_dispatch)` statuses next to the failed `(push)` ones. The combined status of the commit stays `failure`, so the retry cannot turn the bump PR green. The flaw predates the rollout. Kardeema (#2218) works around it: a retry closes the bump PR and recreates it as a new commit, so CI runs fresh on a commit without failed statuses. Plan: https://forgejo.entwirr.me/Wi3eDigital/laravel-deploy-actions/src/branch/main/docs/plan.md ## Tasks - [ ] Confirm on one repo (for example Aevana) that a dispatched CI run leaves the failed `(push)` statuses in place and the combined state stays `failure`. - [ ] Port Kardeema's approach (Kardeema/kardeema `publish_release.yaml`, PR #2218) to Aevana, kima/portal and slight-exposure, or move the bump step into a shared action. - [ ] Also find the bump PR by branch name (`head` filter), not by scanning the first page of open PRs. ## Acceptance criteria - [ ] A flaky CI failure on the bump PR is retried and can end green in every repo using the shared publish flow.
Author
Owner

Confirmed on Aevana from read-only evidence. The mechanism is slightly different from the issue text:

  • release/bump-v0.22.0 (0609bce): run 4597 failed CI / tests (pull_request) at 22:25. The dispatched ci.yaml runs 4598 (cancelled) and 4599 (success, 22:36) posted no status on the commit at all. The combined state stayed failure until run 4597's own job was re-run by hand at 07:14. That rerun wrote to the same context, the state turned success, and the publish run was then re-run. release/bump-v0.6.3 shows the same: dispatched run 2368 left no status.
  • Forgejo uses the latest status per context. A dispatch never writes to the failed context, so the failure cannot clear. Branch protection requires CI / * (Aevana) and CI /* (slight-exposure).
  • Correction: Aevana's and kima's contexts are (pull_request), not (push). No (workflow_dispatch) statuses appeared.

I ported Kardeema#2218: a retry now closes the bump PR, deletes the branch and rebuilds the bump as a fresh commit. CI is judged from the CI / <job> contexts only (per-repo CI_JOBS). The PR is found via pulls/main/{head}.

All three are merged, so I am closing this issue. Not verified end to end: no release run has gone through the new retry yet.

Confirmed on Aevana from read-only evidence. The mechanism is slightly different from the issue text: - `release/bump-v0.22.0` (`0609bce`): run 4597 failed `CI / tests (pull_request)` at 22:25. The dispatched `ci.yaml` runs 4598 (cancelled) and 4599 (success, 22:36) posted **no status** on the commit at all. The combined state stayed `failure` until run 4597's own job was re-run by hand at 07:14. That rerun wrote to the same context, the state turned `success`, and the publish run was then re-run. `release/bump-v0.6.3` shows the same: dispatched run 2368 left no status. - Forgejo uses the latest status per context. A dispatch never writes to the failed context, so the failure cannot clear. Branch protection requires `CI / *` (Aevana) and `CI /*` (slight-exposure). - Correction: Aevana's and kima's contexts are `(pull_request)`, not `(push)`. No `(workflow_dispatch)` statuses appeared. I ported Kardeema#2218: a retry now closes the bump PR, deletes the branch and rebuilds the bump as a fresh commit. CI is judged from the `CI / <job>` contexts only (per-repo `CI_JOBS`). The PR is found via `pulls/main/{head}`. - Aevana/aevana#2024 (merged) - kima/portal#115 (merged) - slight-exposure/slight-exposure#3956 (merged) All three are merged, so I am closing this issue. Not verified end to end: no release run has gone through the new retry yet.
Sign in to join this conversation.
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
Wi3eDigital/laravel-deploy-actions#8
No description provided.