Repository navigation
ci: drop the staging promote and back-sync workflows - #237
Open
spicysouvlaki wants to merge 1 commit into
Open
spicysouvlaki wants to merge 1 commit into
spicysouvlaki wants to merge 1 commit into
Conversation
Since CB-591, browserbase/core builds straight into this repo's main and nothing is written to browserbase-node-staging first. The three workflows that kept the two trunks identical have no job left to do: - stlc-promote.yml fast-forwarded this repo up to staging. It only ever ran on the staging repo. - stlc-sync.yml pulled this repo's main back onto staging twice an hour and pinged staging on each release. - trunk-sync-lock.yml gated staging PRs on the trunks being in sync. Deleting them here also retires the staging copies: the staging repo's next back-sync fast-forwards it to this commit, which removes its own schedule. The staging repo can be archived after that. trunk-release-guard.yml stays for now. Its trunk-synced-release job is a required check on main, so it can only go once the ruleset drops it. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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.
core builds straight into this repo now, so the promote, back-sync and sync-lock workflows have nothing to do. Removing them also stops the staging repo's schedules on its next back-sync, after which
browserbase-node-stagingcan be archived.CI only: no change to the published package.
🤖 Generated with Claude Code