chore: fix weekly TSDiffer when running against baseline that has a version mismatch against latest commit - #10300
Merged
Conversation
|
Build successful! 🎉 |
This reverts commit e9bb254.
|
Build successful! 🎉 |
devongovett
approved these changes
Jul 6, 2026
snowystinger
approved these changes
Jul 6, 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
4 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.
tsdiffer job fails right now since the detected baseline (aka last minor release) doesn't match what is on main (aka patch release version) since we deliberately only look for minor versions to compare against. We do only want to only compare against last minor release so this fixes buildBranchAPI to handle cases like this
✅ Pull Request Checklist:
📝 Test Instructions:
🧢 Your Project:
RSP