Merged
Conversation
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
2 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.
to ruby/prism@c89ca2a
The diff is generated by
tool/sync_default_gems.rb prism. They seem to come from ruby/prism@474ad42, butruby tool/sync_default_gems.rb prism 96eccfc70408c3d26f08f0a523be53cb3dd6d25b..d048418c964da70146fb65c49a50205cc148b7f8doesn't succeed https://github.com/ruby/ruby/actions/runs/18298406027/job/52101460864, so this PR resorts totool/sync_default_gems.rb prism.We should improve
tool/sync_default_gems.rbto avoid failing the sync like that, but now that we've re-enabled the gem sync at ruby/prism#3673, let's start from the clean slate to make sure future sync doesn't fail just because it's already out-of-sync.cc: @kddnewton