Skip to content

ci: add workflow_dispatch to Release #79

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

Merged
ScriptedAlchemy merged 1 commit into from
Sep 16, 2026
+1 −0
Merged

ci: add workflow_dispatch to Release #79

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ name: Release
on:
push:
branches: [main]
workflow_dispatch:

@chatgpt-codex-connector chatgpt-codex-connector Bot Sep 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restrict manual releases to the main branch

A write-capable user can now dispatch this workflow with gh workflow run Release --ref <feature-branch>, causing every release step to check out and operate on an unreviewed ref while retaining contents: write and id-token: write. The gh workflow run documentation defines --ref as the branch or tag containing the workflow version, so a feature branch with a modified package version and no pending changesets can reach the OIDC-enabled npm run release path without passing main-branch review. Gate the release job to refs/heads/main or reject non-main dispatches.

Useful? React with 👍 / 👎.


permissions:
contents: write
Expand Down
Loading