Release SDK updates - #153
Open
kernel-internal[bot] wants to merge 2 commits into
Open
Conversation
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
1 participant
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.
243093b ci: promote through merge-commit pull requests
191223e ci: add stlc promotion workflows
Note
Medium Risk
Changes release automation using admin GitHub App credentials, force-pushes, and auto-merge into production; misconfiguration could affect SDK release timing or branch history, but does not change shipped SDK runtime code.
Overview
Adds GitHub Actions automation for the Stainless staging (
kernel-node-sdk-staging) and production (kernel-node-sdk) Node SDK repos.stlc-promote.ymlruns on pushes to stagingmain. It compares trees withmerge-tree, and when production is behind, force-pushes stagingmainto productionstainless/release, opens a “Release SDK updates” PR if needed, and enables merge-commit auto-merge (explicitly not squash/rebase) so ancestry stays aligned.stlc-sync.ymlcovers the reverse path and hooks: scheduled/eager back-sync of productionmainonto staging (blocked if staging is not an ancestor of production), repository_dispatch from production on release whenSTAGING_DISPATCH_TOKENis set, and on staging pushes a seal-custom-code dispatch tokernel/kernelfor non-generated commits whenCONFIG_DISPATCH_TOKENis set.Reviewed by Cursor Bugbot for commit 243093b. Bugbot is set up for automated code reviews on this repo. Configure here.