fix: update craft workflows to use Sentry release bot credentials#97
Merged
Merged
Conversation
Migrate from the old personal APP_ID/APP_PRIVATE_KEY variables to the Sentry org-standard SENTRY_RELEASE_BOT_CLIENT_ID/SENTRY_RELEASE_BOT_PRIVATE_KEY. Also bump actions/create-github-app-token from v1 to v3.
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
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
APP_ID/APP_PRIVATE_KEY) to the Sentry org-standardSENTRY_RELEASE_BOT_CLIENT_ID/SENTRY_RELEASE_BOT_PRIVATE_KEYactions/create-github-app-tokenfrom v1 to v3Context
The repo was moved from a personal account to
getsentry/. The oldAPP_ID/APP_PRIVATE_KEYvars and secrets no longer exist on the org. The Sentry release bot credentials follow the same pattern used across othergetsentryrepos (e.g.getsentry/cli).Changes
.github/workflows/release.yml— updated app token step.github/workflows/publish.yml— updated app token stepNote
The
SENTRY_RELEASE_BOT_CLIENT_IDvariable andSENTRY_RELEASE_BOT_PRIVATE_KEYsecret need to be configured in the repo settings (or inherited from the org) for the workflows to function.