Repository navigation
fix(release): Prepare releases with the Sentry Release Bot token - #9
Merged
Merged
Conversation
The Release workflow called the reusable Craft workflow, which uses GITHUB_TOKEN for repositories other than getsentry/craft. A push with GITHUB_TOKEN starts no workflows, so the release branch got no CI checks and no `:<sha>` image, and Craft could not publish it. GITHUB_TOKEN also cannot open the publish issue in getsentry/publish. Use the Craft action with a Sentry Release Bot token, as other getsentry repositories do. Co-Authored-By: David Cramer <david@sentry.io>
dcramer
approved these changes
Oct 15, 2026
2 tasks done
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
1 participant
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.
The Release workflow called the reusable Craft workflow. For repositories other than getsentry/craft, that workflow gives Craft
github.token. A push withGITHUB_TOKENstarts no workflows, so therelease/<version>branch gets no CI checks and noghcr.io/getsentry/roach:<sha>image (the changelog commit gives the branch a new SHA). Craft then cannot publish it, and thev<major>tag never moves.GITHUB_TOKENalso cannot open the publish issue in getsentry/publish (publish README). getsentry/shepherd uses the same reusable workflow: its release runs failed, and a person opened the publish issues by hand.This change uses the
getsentry/craft@v2action with a Sentry Release Bot app token. getsentry/action-release, taskbroker, warden, and vitest-evals do the same..craft.ymldoes not change: thegithubtarget withfloatingTags: ["v{major}"]makesv<version>and movesv0. That makesuses: getsentry/roach@v0work.No tag or release exists yet, so
getsentry/roach@v0does not resolve until the first release is published.via David Cramer.
--
View Junior Session [Sentry]