Promote staging to production (a8c1b95) - #670
Merged
Merged
Conversation
Stainless-Generated-From: e188349b22adaa0b17bdfc37d0f2ab59f8037929
Stainless-Generated-From: 713386fec53c76f8b7ffe9ee20a6b33f608a959d
The transferred staging repos live at openlayer-ai/openlayer-<lang>-staging-new, but the shipped stlc-promote.yml / stlc-sync.yml gates named openlayer-<lang>-staging (and openlayer-typescript-staging for TS), so every job was being skipped silently. Point the `github.repository ==` gates and STAGING_REPO at the real slugs and set CONFIG_REPO to the stlc config repo. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XwEaNPPVYspSLwxPo3yquG
The staging repos were renamed openlayer-<lang>-staging-new → openlayer-<lang>-staging (legacy mirrors moved to -staging-old). Update the `github.repository ==` gates and STAGING_REPO accordingly so promote, back-sync and seal-dispatch keep running. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XwEaNPPVYspSLwxPo3yquG
…the integrated line) openlayer-python#667 (Microsoft Agent Framework tracing example) was merged on the production repo directly. Staging is the integrated trunk stlc seals custom code from and the fast-forward back-sync can't apply while the trunks differ, so merge production in by hand; the next build seals the example as custom code. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XwEaNPPVYspSLwxPo3yquG
…dants Production `main` is protected (PR + review) and should stay that way, so the promote no longer force-pushes main. It pushes staging's tip to `stlc/promote` on the production repo and opens/refreshes a PR listing the commits; the PR is the human review gate before publishing and must be merged with a merge commit. Back-sync now also fast-forwards when production is a strict descendant of staging with an identical tree (the merged promote PR), so codegen isn't held between the promote merge and the release commit. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WL7jhZTnnSYDo5vECWpXUw
viniciusdsmello
approved these changes
Sep 9, 2026
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
3 participants
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.
Promotes
openlayer-ai/openlayer-pythonmainto the staging trunk (a8c1b95).Merge with a merge commit — do not squash or rebase. Squashing rewrites the commits and forks the trunks; the next back-sync and promote refuse until repaired by hand.
After merging, release-please opens the version PR on this repo; merging that one tags and publishes.
Commits