gsadmin/sencho
1
0
Fork 0
mirror of https://github.com/Studio-Saelix/sencho.git synced 2026-07-26 11:49:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

ci: add workflow_dispatch trigger to release-please (#865)

Browse Source 
release-please-action v5.0.0 (release-please library 17.6.0) returns
exit code 1 when it tries to create a GitHub Release whose tag already
exists, even when the underlying state is consistent (release already
published, manifest current, label state correct). This causes the
action to abort before the "open or update release PR" step, leaving
new conventional commits unprocessed.

Adding workflow_dispatch lets a maintainer re-run the action manually
from the Actions tab once the inconsistent state is cleared (typically
by removing the autorelease label from the prior release PR), without
needing to push a no-op commit to main to retrigger.

The workflow's internal state checks still run on every dispatch, so
manual triggers cannot double-publish a release. release-please-action
is already at latest (v5.0.0, 2026-04-22) so a version bump is not an
option until upstream ships a fix for the duplicate-tag handling.
This commit is contained in:
Anso
2026-05-01 21:21:19 -04:00
committed by GitHub
parent 344d24698e
commit 7b7edc72bb
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/release-please.yml
+7
View File
@@ -4,6 +4,13 @@ on:
push:
branches:
- main
# Manual recovery lever for cases where the action fails on a transient
# GitHub API issue (e.g. duplicate-release-tag during a retry) and exits
# before scanning main for new conventional commits. Re-running from the
# Actions tab requeues the same logic against the current main HEAD; no
# code push needed. Triggering manually does NOT skip the action's own
# state checks, so it cannot accidentally double-publish a release.
workflow_dispatch:
permissions:
contents: write