release: 0.88.1 - #166
Conversation
ci: use one PR for Node SDK releases
|
🧪 Testing To try out this version of the SDK: Expires at: Wed, 09 Sep 2026 22:07:13 GMT |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 3901085. Configure here.
| --base next --head "$conflict_branch" \ | ||
| --title 'chore: resolve SDK promotion conflict' --body-file "$body") | ||
| echo "::error title=SDK promotion conflict::Resolve the recovery PR: $recovery_url" | ||
| exit 1 |
There was a problem hiding this comment.
Non-atomic conflict recovery race
Medium Severity
On a staging merge conflict, the handler pushes HEAD to next before creating the recovery PR, while the job uses cancel-in-progress: true. A cancel or failure after that push can leave production next advanced without an open stlc/promotion-conflict PR, so conflicting staging changes are not queued for resolution until a later retry happens to recreate it.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 3901085. Configure here.


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 affect how SDK versions reach npm (promotion + release-please + GitHub release), so a mis-merge or workflow bug could block or mis-ship releases; runtime SDK behavior is unchanged aside from the version constant.
Overview
This PR cuts release 0.88.1 (
package.json,src/version.ts, manifest, changelog) and ships the release/promotion workflow updates that go with it.Release automation no longer relies on the stock
googleapis/release-please-actiononmainonly. Pushes tonextbuild a pinned stainless-api/release-please CLI and runrelease-pr(next→main); pushes tomainrungithub-release. Legacystainless/releasePRs/branches are closed and deleted. A workflow concurrency group serializes release-please runs, andrelease-please-config.jsonadds merge-commit guidance in the release PR footer.Staging promotion (
stlc-promote) stops force-pushingstainless/releaseand opening auto-merge promote PRs. It merges productionmainand stagingmaininto a branch based onproduction/next(ormainifnextis missing), pushesproduction/next, and on merge failure opens a draft recovery PR onstlc/promotion-conflictinstead of attempting silent auto-merge.The 0.88.1 changelog entry is link-only (no new feature bullets in this bump).
Reviewed by Cursor Bugbot for commit 3901085. Bugbot is set up for automated code reviews on this repo. Configure here.