docs: simplify the SDK release flow - #386
Open
sjmiller609 wants to merge 2 commits into
Open
Conversation
-->
✱ stlc build✅ go code · compare
✅ typescript code · compare
Diagnostics: 💡 0 new / 5 total note
Build metadata
This comment is auto-generated by stlc and is kept up to date as you push. |
sjmiller609
marked this pull request as ready for review
August 10, 2026 20:42
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
nextnext→mainPR as the only manual release actionTesting
Rollout
Merge the SDK staging workflow PRs before this PR so the next generation run uses the single-PR flow.
Note
Low Risk
Documentation and comment-only changes with no runtime or workflow logic modified.
Overview
Updates SDK generation docs to match the simplified release model: staging promotion advances public
next, and release automation maintains one versionednext→mainPR per SDK (replacing the oldstainless/release+ release-please steps).The stlc-generate workflow header and
docs/runbooks/sdk-generation-stlc.mdnow describe accumulating changes onnext, merging that release PR with a merge commit to publish, and opening a draft recovery PR onnextwhen promotion hits Git conflicts. Normal API change guidance and the hosted cutover checklist use the samepreview → staging → next → release PR → publish → back-syncwording.Reviewed by Cursor Bugbot for commit 88d4381. Bugbot is set up for automated code reviews on this repo. Configure here.