Skip to content

release: 10.5.0 - #671

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

release: 10.5.0#671
stainless-app[bot] wants to merge 7 commits into
mainfrom
release-please--branches--main--changes--next--components--finch-api

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

10.5.0 (2026-07-30)

Full Changelog: v10.4.0...v10.5.0

Features

Bug Fixes

  • stlc: stop hand-edited CI workflows from blocking seals and builds (74d7c0a)

Chores

  • internal: codegen related update (558ccd1)

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

@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--finch-api branch from 65d0da2 to 67ce589 Compare July 29, 2026 14:46
@stainless-app stainless-app Bot changed the title release: 10.4.1 release: 10.5.0 Jul 29, 2026
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--finch-api branch from 67ce589 to 2865f1a Compare July 29, 2026 14:47
stainless-app Bot added 2 commits July 30, 2026 19:16
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
stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--finch-api branch from 2865f1a to 86b70c6 Compare July 30, 2026 19:16
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.

0 participants