Release SDK updates - #147
Open
kernel-internal[bot] wants to merge 3 commits into
Open
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b94cd58. Configure here.
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.

f026272 ci: harden promotion pull request updates
b94cd58 ci: promote through merge-commit pull requests
9e39767 ci: add stlc promotion workflows
Note
Medium Risk
Automation writes to the production SDK repo (GitHub App token, force-push to
stainless/release, auto-merge); misconfiguration or ancestry drift could block sync or require manual promotion.Overview
Adds GitHub Actions to move the Go SDK between staging (
kernel-go-sdk-staging) and production (kernel-go-sdk) while keeping a single ancestry line (merge commits only, no squash on promote).stlc-promote.ymlruns on stagingmainpushes: skips when production’s tree already matches staging, otherwise force-pushes stagingmainto production’sstainless/release, creates or updates a “Release SDK updates” PR into productionmain(body = commit list), and enables auto-merge with a merge commit (warns if that fails).stlc-sync.ymladds the reverse path and hooks: back-sync (cron, manual, orprod-releaseddispatch) fast-forwards stagingmainfrom production when staging is behind, with an ancestor check before push; notify-back-sync from production on release optionally pings staging; seal-dispatch on staging pushes (non–Stainless-generated commits) optionally notifies the config repo viaseal-custom-code.Reviewed by Cursor Bugbot for commit f026272. Bugbot is set up for automated code reviews on this repo. Configure here.