Backport(v1.16) ci: use latest rubygems again for Ruby 3.1 on windows (#4750)#4803
Merged
Backport(v1.16) ci: use latest rubygems again for Ruby 3.1 on windows (#4750)#4803
Conversation
**Which issue(s) this PR fixes**: Backport #4750 **What this PR does / why we need it**: It seems that it fixes failure with Ruby 3.1 on windows. ``` undefined method `ignored?' for #<Gem::Specification:0x000001dccaf43168 ``` NOTE: Initially introduced by #4681, then reverted in #4746. Thus, it's a side-effect of #4760. **Docs Changes**: N/A **Release Note**: N/A Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
daipom
approved these changes
Jan 29, 2025
Contributor
|
Thanks! |
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
3 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.
Which issue(s) this PR fixes:
Backport #4750
What this PR does / why we need it:
It seems that it fixes failure with Ruby 3.1 on windows.
NOTE: Initially introduced by #4681, then reverted in #4746. Thus, it's a side-effect of #4746.
Docs Changes:
N/A
Release Note:
N/A