Skip to content

Release SDK updates - #12

Merged
yongpark merged 11 commits into
mainfrom
stainless/release
Jun 30, 2026
Merged

yongpark merged 11 commits into
mainfrom
stainless/release

Conversation

@justinHe123

Copy link
Copy Markdown
Contributor

960996c Add cost_effective 2026-06-26: degenerate-early-stop fallback + side-by-side table rule (#21115)

stlc-bot and others added 11 commits June 26, 2026 03:15
…by-side table rule (#21115)

Stainless-Generated-From: 330715882bb854fbaf79e9eef4dfea3e70f9a7f6
Stainless-Generated-From: abbc4d1601e1c743455990cb7e55799220dece51
Stainless-Generated-From: d6f22be8336a869c5e2479fd0b86dfec027b4036
Stainless-Generated-From: 5e982f7908e22cc6dd5ee4c2957bc2305a7fafd1
Stainless-Generated-From: ab436ff0f1ca47d2cb93d8356849cf56ca9b35b4
The sync-from-production push was rejected because it tried to create
production-only workflow files (release.yml / publish-*.yml) on staging,
which a GitHub App token (GITHUB_TOKEN) may not do. Squash production's
content into one commit that keeps staging's own .github/workflows/, so
the push is workflow-free and accepted, while still back-syncing the
release-please content.
The first cut used `git reset --hard production/main`, which replaces
staging's tree with production's. Staging is ahead of production on
generated code, so that reverted staging (e.g. dropped webhookSigningSecret).
Use `git merge --squash` so staging keeps its newer code and only gains
production's release-please commits, still as one workflow-free commit.
Sync release changes from production
main is unprotected and the bot PR's CI is gated behind manual approval, so
--auto (which waits on checks) never completes. Immediate merge is hands-off
and needs no approval.
Stainless-Generated-From: 5758524622e84d5eb5e1d022ee0a66694db31ff2
@yongpark
yongpark merged commit 19ecf8d into main Jun 30, 2026
3 checks passed
llama-org-ci-bot Bot added a commit that referenced this pull request Aug 23, 2026
Sync release changes from production
@llama-org-ci-bot llama-org-ci-bot Bot mentioned this pull request Aug 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants