fix: bump Fable.Core to 5.0.0-rc.2 and ShipIt to 2.0.2#243
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This was referenced Apr 16, 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
1 participant
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.
Summary
Fable.Coreto 5.0.0-rc.2EasyBuild.ShipItto 2.0.2Uses
fix:so that merging triggers the ShipIt release workflow and cuts the next5.0.0-rc.*release. Since the last tagged release (v5.0.0-rc.2), the unreleased range onmainhas beenchore:-only, which ShipIt ignores for version bumps — this PR gives it a patch-worthy commit to act on.Test plan
just buildsucceeds against Fable.Core 5.0.0-rc.2just test-pythonpassesShipIt - Pull Requestjob opens achore: release ...PR🤖 Generated with Claude Code