Repository navigation
ci: drop the trunk release guard - #238
Draft
spicysouvlaki wants to merge 1 commit into
Draft
spicysouvlaki wants to merge 1 commit into
spicysouvlaki wants to merge 1 commit into
Conversation
trunk-release-guard.yml blocked a release PR while browserbase-node-staging had commits this repo lacked, so a release could not ship before the promote ran (the 2026-08-24 v2.18.1 incident). Nothing writes to the staging repo any more: core builds straight into main here, so staging can never be ahead and the guard always passes. Its trunk-synced-release job is a required status check on main. The ruleset has to drop that check before this merges, or every PR to main waits on a check that never reports. 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.
The guard compares
mainwithbrowserbase-node-staging, which nothing writes to any more, so it always passes. Stacked on #237.Do not merge until the
mainruleset stops requiringtrunk-synced-release, or every PR tomainblocks on a check that never reports.🤖 Generated with Claude Code