Skip to content

ci: read the release deploy key from a main-only environment #14

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
Mearman merged 1 commit into from
Oct 12, 2026
Merged

ci: read the release deploy key from a main-only environment #14

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
2 changes: 2 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -274,6 +274,8 @@ jobs:
# Deliberately a GitHub-hosted runner, not the resolved one: npm trusted publishing only works from GitHub-hosted runners, so the OIDC token exchange cannot happen on the self-hosted fleet or Blacksmith.
runs-on: ubuntu-latest
timeout-minutes: 15
# The deploy key lives in this environment, whose deployment branches are limited to main, so no other branch's workflow can read it.
environment: release
permissions:
contents: write # to push the release commit and tag and create the GitHub Release
issues: write # to comment on released issues
Expand Down