release: 0.88.1 - #160
Open
stainless-app[bot] wants to merge 6 commits into
Open
Conversation
ci: use one PR for Go SDK releases
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Wed, 09 Sep 2026 22:07:12 GMT |
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.
Automated Release PR
0.88.1 (2026-08-10)
Full Changelog: v0.88.0...v0.88.1
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Note
Medium Risk
Changes production release and staging promotion CI paths; mistakes could block releases or push bad merges to
next, though conflict handling adds a manual recovery path.Overview
Release 0.88.1 bumps the published SDK version (
internal/version.go, README pin, manifest, changelog).The substantive changes rework how staging reaches production:
Release Please no longer uses
googleapis/release-please-actiononmainalone. It runs onnextandmain, builds a pinnedstainless-api/release-pleaseCLI, opens/updates a versioned PR fromnext→main, closes legacystainless/releasePRs, and creates the GitHub release whenmainis updated.Promote SDK changes stops force-pushing
stainless/releaseand auto-opening/merging a generic promote PR. It now merges productionmainand validated staging into anextbranch, pushesnext, and on merge conflicts opens a draft recovery PR onstlc/promotion-conflict.release-please-config.jsonadds a PR footer instructing merge-commit merges so release + publish run correctly.Reviewed by Cursor Bugbot for commit 680faf4. Bugbot is set up for automated code reviews on this repo. Configure here.