-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop Support Ruby 3.0 #217
base: main
Are you sure you want to change the base?
Conversation
If you could rebase this and update the dependencies again, I can give this a review! |
Rebase done 👍 |
discordrb.gemspec
Outdated
spec.add_development_dependency 'rspec-prof', '~> 0.0.7' | ||
spec.add_development_dependency 'rubocop', '~> 1.36.0' | ||
spec.add_development_dependency 'rubocop', '~> 1.48.0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
spec.add_development_dependency 'rubocop', '~> 1.48.0' | |
spec.add_development_dependency 'rubocop', '~> 1.52.0' |
Just need to update to the latest RuboCop version and apply any new changes it looks like.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Though it looks like there's some false positives due to rubocop/rubocop#11915, so watch out for these.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'd been on 1.36 for over 7 months, and in Rubocop's changelogs there are constant "false positives" and even "false negatives" between each version.
I just put the most recent one at a given time (when I started working on this PR), which solved the problems in Ruby 3.x
Not to mention that before this PR becomes part of "main", there'll be a certain amount of time in between. I'm not going to come back and increment the version number regularly, I'll do it if it's really necessary, but in due time.
fee010c
to
97fba3f
Compare
8883f97
to
fc17b64
Compare
+ Rspec tasks (for Ruby 2.7.x, 3.0.x, 3.1.x, 3.2.x) + Rubocop task (with Ruby 2.7.x) + Yard & Github pages tasks (with Ruby 2.7.x) + Update rspec version constraint in discordrb.gemspec (from ~> 3.11.0 to ~> 3.12.0) + Update redcarpet version constraint in discordrb.gemspec (from ~> 3.5.0 to ~> 3.6.0)
Finally, after doing my tests on the latest version of Rspec, and looking at the code, I realize that the modification was not necessary, and PixeLInc was right in his PR shardlab#199
Contrary to what the documentation indicated, it was not possible to provide an Array<Overwrite> to Channel#permission_overwrites= It was necessary to provide the Hash similar to what the method Channel#permission_overwrites returns + Added an example file to test the overwrites (I used it as a debug) + Modification of a test in spec/data/channel_spec.rb following this correction
Fix typo and newlines Co-authored-by: Adrien Smith <[email protected]>
Summary
Pull request to drop support of Ruby 3.0 (Previously 2.7)
Base on PR #216
Changed