Skip to content

release: 3.1.0-rc.2 - #250

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

release: 3.1.0-rc.2#250
stainless-app[bot] wants to merge 5 commits into
mainfrom
release-please--branches--main--changes--next--components--writer-sdk

Conversation

@stainless-app

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

Copy link
Copy Markdown
Contributor

Automated Release PR

3.1.0-rc.2 (2026-08-14)

Full Changelog: v3.1.0-rc.1...v3.1.0-rc.2

Features

  • stlc: configurable CI runner and private-production-repo support in workflow templates (67aca81)

Bug Fixes

  • ci: bump @arethetypeswrong/cli to ^0.18.0 and run CI workflows on Node 24 (f817075)
  • stlc: stop hand-edited CI workflows from blocking seals and builds (10695ce)

Chores

  • internal: codegen related update (d6023e4)

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--writer-sdk branch from 037149c to 7448988 Compare July 17, 2026 17:17
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--writer-sdk branch from 7448988 to a827670 Compare July 28, 2026 19:01
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--writer-sdk branch from a827670 to 7b25043 Compare August 14, 2026 21:39
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