Merged
Conversation
Danger ReportNo issues found. |
ericproulx
force-pushed
the
exclude_ruby_3_2_rails_edge
branch
from
9e95dcb to
daee5ad
Compare
ericproulx
changed the title
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.
Exclude Ruby 3.2 from Rails edge CI matrix
Summary
ruby: 3.2+gemfile: rails_edgecombination from the edge CI matrix.Motivation
Rails edge has dropped support for Ruby 3.2, causing that combination to fail in CI. Since the
edgeworkflow runs withcontinue-on-error: truethese failures are non-blocking, but excluding the unsupported combination avoids the noise and keeps the matrix accurate.See https://github.com/ruby-grape/grape/actions/runs/24068853024