docs(sdk): Update cutting-a-release playbook to use GitHub Actions only#16831
Draft
docs(sdk): Update cutting-a-release playbook to use GitHub Actions only#16831
Conversation
Replace CLI invocation of Craft (craft prepare / craft publish) with the GitHub Actions workflow approach. All SDK repos trigger releases exclusively through CI via workflow_dispatch — never from a local machine. Also correct the publish flow description: the approval mechanism is an issue in getsentry/publish labeled 'accepted', not a PR merge. Add a step for polishing the release branch changelog, and make the two-person approval requirement explicit. Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
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.
DESCRIBE YOUR PR
Updates the "Cutting a Release" playbook to reflect that all Sentry SDK releases are triggered exclusively through GitHub Actions — never via local
craft prepare/craft publishCLI invocations.Changes:
craft prepare <version>bash block with GitHub Actions UI instructions (Actions tab → find workflow → Run workflow)version: autoinput option supported by several SDKsgetsentry/publishlabeledaccepted, not a PR mergeIS YOUR CHANGE URGENT?
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: