Remove Ruby 3.1 specific workaround from CI workflow#8950
Merged
deivid-rodriguez merged 1 commit intomasterfrom Sep 2, 2025
Merged
Remove Ruby 3.1 specific workaround from CI workflow#8950deivid-rodriguez merged 1 commit intomasterfrom
deivid-rodriguez merged 1 commit intomasterfrom
Conversation
deivid-rodriguez
force-pushed
the
deivid-rodriguez/small-ci-tweaks
branch
2 times, most recently
from
62aa61d to
0fe1149
Compare
deivid-rodriguez
changed the title
deivid-rodriguez
added a commit
that referenced
this pull request
Sep 4, 2025
Remove Ruby 3.1 specific workaround from CI workflow (cherry picked from commit 44a8868)
deivid-rodriguez
added a commit
that referenced
this pull request
Sep 9, 2025
Remove Ruby 3.1 specific workaround from CI workflow (cherry picked from commit 44a8868)
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.
What was the end-user or developer problem that led to this PR?
None, just noticed this is no longer necessary.
What is your fix for the problem, implemented in this PR?
Remove the unnecessary workaround.
Make sure the following tasks are checked