Skip to content

release: 0.88.1 - #166

Open
stainless-app[bot] wants to merge 6 commits into
mainfrom
release-please--branches--main--changes--next--components--sdk
Open

release: 0.88.1#166
stainless-app[bot] wants to merge 6 commits into
mainfrom
release-please--branches--main--changes--next--components--sdk

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

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-action on main only. Pushes to next build a pinned stainless-api/release-please CLI and run release-pr (nextmain); pushes to main run github-release. Legacy stainless/release PRs/branches are closed and deleted. A workflow concurrency group serializes release-please runs, and release-please-config.json adds merge-commit guidance in the release PR footer.

Staging promotion (stlc-promote) stops force-pushing stainless/release and opening auto-merge promote PRs. It merges production main and staging main into a branch based on production/next (or main if next is missing), pushes production/next, and on merge failure opens a draft recovery PR on stlc/promotion-conflict instead 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.

@stainless-app

stainless-app Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

🧪 Testing

To try out this version of the SDK:

npm install 'https://pkg.stainless.com/s/kernel-typescript/e966d47d43ac9a3f978830200b963b48fe33f8fd/dist.tar.gz'

Expires at: Wed, 09 Sep 2026 22:07:13 GMT
Updated at: Mon, 10 Aug 2026 22:07:13 GMT

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

Fix All in Cursor

❌ 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

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 3901085. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant