Skip to content

ci: allow the release workflow to be triggered manually #932

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
robdecker wants to merge 2 commits into
base: main
Choose a base branch
from
Open

ci: allow the release workflow to be triggered manually #932

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
399d2c5
ci: allow the release workflow to be triggered manually
robdecker Sep 22, 2026
e2aa917
ci: only release from main, now that the workflow can be run by hand
robdecker Sep 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 21 additions & 2 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,11 @@ on:
push:
branches:
- main
# Manual trigger. A run that fails at startup (a workflow file the runner
# rejects, an action the repository does not allow) cannot be re-run, and
# `main` takes no direct pushes, so without this the only way to retry is
# to merge another pull request.
workflow_dispatch:

# Default to read-only. Each job widens only what it needs.
permissions:
Expand All @@ -22,7 +27,15 @@ jobs:
release-please:
runs-on: ubuntu-latest
timeout-minutes: 10
if: github.repository == 'chapter-three/next-drupal'
# The ref check is a security control, not a tidy-up. A manual run lets
# whoever starts it pick the branch, and both this file and the checked-out
# code would then come from that branch, while npm's trusted publisher
# matches on repository and workflow filename rather than on ref. Without
# this, anyone with write access could publish from a branch nobody
# reviewed. Releases come from `main` or they do not happen.
if: >-
github.repository == 'chapter-three/next-drupal' &&
github.ref == 'refs/heads/main'
# No permissions block: both steps authenticate with the app token, so the
# job's own GITHUB_TOKEN stays at the workflow default of contents: read.
# The app's permissions are set on the app itself, not here.
Expand Down Expand Up @@ -58,7 +71,13 @@ jobs:
# automatically, so no --provenance flag is needed.
publish:
needs: release-please
if: needs.release-please.outputs.releases_created == 'true'
# Skipping release-please already skips this job, since its output would be
# empty. The ref check is repeated anyway: this is the job that holds
# id-token and can publish, so it should not depend on another job's
# condition to stay on `main`.
if: >-
needs.release-please.outputs.releases_created == 'true' &&
github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
timeout-minutes: 15
permissions:
Expand Down
Loading