Skip to content

fix(release): approve the held CI runs of release pull requests - #29

Merged
vannt-dev merged 1 commit into
mainfrom
fix/approve-release-pr-runs
Sep 28, 2026
Merged

vannt-dev merged 1 commit into
mainfrom
fix/approve-release-pr-runs

Conversation

@vannt-dev

Copy link
Copy Markdown
Owner

Correction to #27, found by watching it run on this repository's release PR, #28.

Changes:

  • release-pr-ci now looks up actions/runs?branch=<release branch>&event=pull_request&status=action_required, retrying for up to a minute because the runs appear just after the PR event, and approves each one. The job is added whenever the release module is on, since any pull_request workflow may be held.
  • The generated ci.yml drops workflow_dispatch again.
  • README and the pr_branch output description say what actually happens.

The standard stays 1.4.0, which hasn't been released yet (#28 is still open).

Checks: typecheck, biome, 278/278 tests, repokeeper check matches, actionlint clean. After merge, release-please updates #28 with GITHUB_TOKEN. That run tests the job for real, including whether GITHUB_TOKEN with actions: write may approve runs.

🤖 Generated with Claude Code

…ad of dispatching CI

GitHub does create pull_request runs for a pull request that GITHUB_TOKEN
opened, but holds them as action_required until someone approves them.
Runs started through workflow_dispatch land on the same commit yet don't
count for the pull request: on repokeeper#28 its status check rollup stayed
null until the held run was approved. release-pr-ci now approves those runs,
and ci.yml no longer needs workflow_dispatch.
@vannt-dev
vannt-dev merged commit 1c87d86 into main Sep 28, 2026
19 checks passed
@vannt-dev
vannt-dev deleted the fix/approve-release-pr-runs branch September 28, 2026 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant