Repository navigation
Require SDK release tags to reference protected main commits - #53
Merged
Merged
Conversation
stephenvapiai
approved these changes
Nov 3, 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
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.
A version-matching tag could previously publish SDK code that had never reached protected
main. Before package installation or building, fetchmain, resolve the event commit (including annotated tags), verify the checkout matches it, and require that commit to be an ancestor ofmain. Older approved commits remain eligible for backports.Preserve the new guard through Fern regeneration and test it with actual Git histories covering approved ancestors, annotated tags, unmerged commits, incorrect checkouts, missing refs, and branch refs masquerading as tags. Existing tag/version validation and isolated npm publishing remain in place.
Validation: all 25 release-validation tests pass locally. GitHub compile/test checks passed on both push and pull-request runs. No release tag was created and no package was published.
The repository rule was separately updated to dismiss stale approvals after code changes; its one-approval requirement, required compile/test checks, and empty bypass list remain in place.