Skip to content

fix(T12094): grant actions:write so the CI dispatch can actually fire - #1185

Merged
kryptobaseddev merged 2 commits into
mainfrom
fix/T12094-actions-write
Aug 11, 2026
Merged

fix(T12094): grant actions:write so the CI dispatch can actually fire#1185
kryptobaseddev merged 2 commits into
mainfrom
fix/T12094-actions-write

Conversation

@kryptobaseddev

Copy link
Copy Markdown
Owner

The dispatch step from #1182 was correct but couldn't run. Measured on the v2026.8.5 release:

could not create workflow dispatch event:
HTTP 403: Resource not accessible by integration

Creating a workflow_dispatch event needs actions: write; the workflow declared only contents, pull-requests, id-token. So the bump-PR still opened with zero checks.

Worth noting the step's graceful degradation paid off: because it warns instead of failing, the release completed and told us exactly why, rather than dying at the last step with a bare non-zero exit.

Template parity passes in --strict.

🤖 Generated with Claude Code

kryptobaseddev and others added 2 commits August 10, 2026 20:55
The dispatch step shipped in #1182 was correct but could not run. Measured on the
v2026.8.5 release:

    could not create workflow dispatch event:
    HTTP 403: Resource not accessible by integration

Creating a `workflow_dispatch` event requires `actions: write`, and the workflow
declared only `contents`, `pull-requests` and `id-token`. So the bump-PR still
opened with no checks — the exact failure the step exists to prevent.

The step's graceful degradation earned its keep: because it warns rather than
fails, the release completed and named the cause precisely instead of dying at
the last step with a bare non-zero exit.

Verified: both files now parse with `actions: write`, and template parity passes
in `--strict`.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This is the last thing blocking an unattended release, and it is the same root
cause one layer down.

v2026.8.5's bump-PR was BLOCKED by the Worktree NAPI Prebuild Gate:

    Found prebuild run #31456705101 (status: completed)
    ✗ worktree-napi prebuild completed with conclusion: action_required

`action_required` does not mean the build failed. It means GitHub queued the run
pending human approval — which is the state of EVERY run triggered by a
GITHUB_TOKEN-created `pull_request`, i.e. every release bump-PR. The gate treated
any non-`success` conclusion as failure, so it reported a build failure for a
build that had never been permitted to start.

Two changes, both addressing the cause rather than the symptom:

1. The gate now recognises `action_required`, APPROVES the run, and waits for the
   real result. `actions: write` is granted on that job so it can. If the token
   still cannot approve, it prints the exact `gh api -X POST …/approve` command
   instead of a misleading failure.

2. `release-prepare` now dispatches `worktree-napi-prebuild.yml` for the release
   branch alongside `ci.yml`. An explicit dispatch is not subject to the approval
   gate, so the prebuild produces a real conclusion in the first place and the
   approval path becomes a fallback rather than the norm.

Verified: `ci.yml` parses, the gate job carries `actions: write`, template parity
passes `--strict`, and gate 15 confirms every `cleo` verb in the workflows exists.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kryptobaseddev
kryptobaseddev merged commit bc07655 into main Aug 11, 2026
76 checks passed
@kryptobaseddev
kryptobaseddev deleted the fix/T12094-actions-write branch August 11, 2026 05:19
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