From e9d81033cb4e37694ca62c989757f771bc0ffbeb Mon Sep 17 00:00:00 2001 From: Yasunobu <42543015+P4suta@users.noreply.github.com> Date: Tue, 4 Aug 2026 19:58:13 +0900 Subject: [PATCH] fix: give the release workflow a manual retry path The first run of the new workflow failed at startup, because release-plz/action was not in this repository's allowed-actions list: The action release-plz/action@2eb1d8bc... is not allowed in P4suta/windows-spawn because all actions must be from a repository owned by P4suta, created by GitHub, or match one of the patterns The list has been corrected. What the failure exposed is that there was no way to try again: a run that fails at startup is not retryable, and with `on: push` alone the only other trigger is a commit landing on main, which goes through a pull request. A release that fails for a transient or configuration reason would have needed a no-op commit to retry. Add workflow_dispatch. It is not a second way to release: release-plz still publishes only when the manifest version is ahead of the registry, so dispatching from main when nothing is pending does nothing. Co-Authored-By: Claude Fable 5 --- .github/workflows/release-plz.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/release-plz.yml b/.github/workflows/release-plz.yml index 5da0fba..3971d23 100644 --- a/.github/workflows/release-plz.yml +++ b/.github/workflows/release-plz.yml @@ -19,6 +19,12 @@ name: Release-plz "on": push: branches: [main] + # A release that fails partway cannot be recovered by re-running: a run that + # fails at startup is not retryable, and `main` only moves through pull + # requests. Manual dispatch is the retry path. It is not a second way to + # release -- release-plz still publishes only when the manifest version is + # ahead of the registry. + workflow_dispatch: permissions: {}