fix: align release-please with infra OIDC publish setup - #5
Merged
Conversation
Use org AMPLITUDE_DEV_EXP GitHub App secrets (same as Amplitude-TypeScript), npm-release environment for Trusted Publishing, and Node 24 for OIDC-capable npm. Co-authored-by: Cursor <cursoragent@cursor.com>
daniel-graham-amplitude
self-requested a review
July 29, 2026 21:18
daniel-graham-amplitude
approved these changes
Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Wire
release-please.ymlto the infra-standard publish path:AMPLITUDE_DEV_EXP_APP_ID/AMPLITUDE_DEV_EXP_PRIVATE_KEY(same as Amplitude-TypeScript publish-v2.yml)npm-release(matches Trusted Publishing config + existing repo environment)NPM_TOKEN)Previously the workflow referenced non-existent
RELEASE_PLEASE_*secrets andnpm-publishenvironment.Infra prerequisite
Org secrets must grant
amplitude/developer-cliaccess toAMPLITUDE_DEV_EXP_*(infra indicated Trusted Publishing is already configured forrelease-please.yml+npm-release).After merge
mainfeat:)betatagTest plan
npm-releaseenv and publishes with provenanceMade with Cursor