fix(release): grant actions:write on callers of release.yml (#1341)

release.yml's publish-release job got `actions: write` in f6cc2aee so it
can dispatch homebrew-bump.yml, but reusable-workflow permissions are
capped by the caller. release-cut.yml and release-rc.yml only listed
`contents: write`, so the first cut after f6cc2aee died with
startup_failure (run 25244518794) before any job could start.

Grant `actions: write` on both callers to match what release.yml needs.

Co-authored-by: Orca <help@stably.ai>
This commit is contained in:
Neil 2026-05-01 22:34:26 -07:00 committed by GitHub
parent 1db7839570
commit 74a7a3c790
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 12 additions and 0 deletions

View File

@ -39,6 +39,13 @@ on:
permissions:
contents: write
# Why: this workflow calls release.yml, whose publish-release job needs
# actions: write to dispatch homebrew-bump.yml. Reusable workflows are
# capped by the caller's permissions, so the caller must list every
# scope the callee needs. Omitting this produced a startup_failure on
# run 25244518794 immediately after actions:write was added to
# release.yml in f6cc2aee.
actions: write
concurrency:
group: release-cut

View File

@ -17,6 +17,11 @@ on:
permissions:
contents: write
# Why: this workflow calls release.yml, whose publish-release job needs
# actions: write to dispatch homebrew-bump.yml. Reusable workflows are
# capped by the caller's permissions, so the caller must list every
# scope the callee needs. Mirrors the fix in release-cut.yml.
actions: write
concurrency:
group: release-rc