Conversation
alpaca-tc
force-pushed
the
1.3-drop-rails-6-0
branch
from
1dae7de to
cc0ab4d
Compare
Merged
Member
|
Thanks for the PR 😃 |
Contributor
Author
|
@winebarrel changed! |
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.
I drop support for Rails 5.1+5.2+6.0 and removed the code.
I am going to create a PR that will support Rails 7.1.
7.1 will have destructive changes, so some tests will need new
cond(">= 7.1", ...)code.I would like to cut off support for older rails, which is already EOL because of the complexity of the tests. What do you think?
NOTE: I don't think this PR should be merged into the minor version. I would be happy to create a new major version(2.0) branch.