Skip to content

ci(release): gate publishing behind an approval environment #56

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
rpvilo merged 1 commit into from
Aug 3, 2026
Merged

ci(release): gate publishing behind an approval environment #56

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
9 changes: 9 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,15 @@ permissions:
jobs:
release:
runs-on: ubuntu-latest
# Proof-of-presence for publishing. A push to main can reach npm without any
# stored credential (OIDC), so "who can push to main" would otherwise mean
# "who can publish". This environment requires a human to approve the run in
# the Actions UI before the job starts, and is restricted to main.
#
# It gates the whole job, including the version step. When only a Version
# Packages PR is being opened, approve it the same way — the job does not
# distinguish, and approving costs one click.
environment: npm-publish
steps:
- uses: actions/checkout@v4

Expand Down
Loading