Skip to content

fix: read GitHub App secrets from npm-release environment #6

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
ekim-amplitude merged 1 commit into from
Jul 29, 2026
Merged

fix: read GitHub App secrets from npm-release environment #6

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
7 changes: 5 additions & 2 deletions .github/workflows/release-please.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,14 +14,17 @@ permissions:
jobs:
release-please:
runs-on: ubuntu-24.04
# AMPLITUDE_DEV_EXP_* live on the npm-release environment (same as
# Amplitude-TypeScript publish-v2.yml), not repo/org secrets.
environment: npm-release
outputs:
releases_created: ${{ steps.release.outputs.releases_created }}
steps:
# Mint a GitHub App installation token so release-please's PRs trigger
# downstream workflows (GITHUB_TOKEN-authored events do not, by design,
# which would leave required checks unrun and the Release PR BLOCKED).
# Org secrets (shared with Amplitude-TypeScript / wizard release automation).
# Infra must grant amplitude/developer-cli access to these org secrets.
# Requires AMPLITUDE_DEV_EXP_APP_ID + AMPLITUDE_DEV_EXP_PRIVATE_KEY on the
# npm-release environment (infra copies from Amplitude-TypeScript).
- uses: actions/create-github-app-token@df432ceedc7162793a195dd1713ff69aefc7379e # v2.0.6
id: app-token
with:
Expand Down
Loading