release: 1.2.0 - #24
Open
stainless-app[bot] wants to merge 7 commits into
Open
Conversation
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Sun, 30 Aug 2026 02:09:39 GMT |
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--parallel-web
branch
from
July 11, 2026 02:17
ca8a29d to
047453c
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--parallel-web
branch
from
July 11, 2026 02:18
047453c to
084cb74
Compare
…t in workflow templates
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--parallel-web
branch
from
July 18, 2026 02:12
084cb74 to
dc3ed70
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--parallel-web
branch
from
July 18, 2026 02:12
dc3ed70 to
d0e9066
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--parallel-web
branch
from
July 29, 2026 02:16
d0e9066 to
49de4af
Compare
Editing the generated CI/release workflows in an SDK repo is supported: stlc writes them once and then leaves them under the repo's ownership. Two safety checks did not account for that and could refuse to seal custom code, or refuse to build, over workflow edits that were never at risk of being overwritten. The seal refusal could not be cleared by rebuilding. Sealing is also now recorded in place rather than under a new filename each time, so an interrupted build can no longer leave a workspace with no record of its sealed custom code, and sealing one branch no longer discards the record for another.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--parallel-web
branch
from
July 31, 2026 02:09
49de4af to
7ef255e
Compare
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.
Automated Release PR
1.2.0 (2026-07-31)
Full Changelog: v1.1.0...v1.2.0
Features
Bug Fixes
Chores
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