Skip to content

Bump Rubocop TargetRubyVersion to 2.5 series#78

Merged
GustavoCaso merged 2 commits intomasterfrom
bump-rubocop-ruby-target-version
Apr 20, 2021
Merged

Bump Rubocop TargetRubyVersion to 2.5 series#78
GustavoCaso merged 2 commits intomasterfrom
bump-rubocop-ruby-target-version

Conversation

@sambostock
Copy link
Copy Markdown
Contributor

Ruby 2.4 is EOL and Rubocop has accordingly dropped their support. This change fixes our CI.

Relevant Links

Ruby 2.4 is EOL and Rubocop has accordingly dropped their support.

https://www.ruby-lang.org/en/news/2020/04/05/support-of-ruby-2-4-has-ended/
rubocop/rubocop#9648
https://github.com/rubocop/rubocop/blob/76bc0a0e026b13fccdc7b6bccfd6d082d24a7b52/CHANGELOG.md#1130-2021-04-20

The change to the TargetRubyVersion introduced a violation because of
the redundant `begin`, which has been autocorrected.
@sambostock sambostock force-pushed the bump-rubocop-ruby-target-version branch from 1a8a890 to c6441db Compare April 20, 2021 16:27
@sambostock sambostock requested a review from GustavoCaso April 20, 2021 16:33
@rafaelfranca
Copy link
Copy Markdown
Member

Should we drop support to 2.4 in the gem? It is still allowed to be installed in 2.4

Since we no longer lint against 2.4 syntax, we should explicitly drop
support for it.
@sambostock
Copy link
Copy Markdown
Contributor Author

Good idea @rafaelfranca. I just pushed a commit doing that. Hopefully that is the correct way to specify it?

@sambostock
Copy link
Copy Markdown
Contributor Author

sambostock commented Apr 20, 2021

Though, it does occur to me: is dropping 2.4 support a breaking change, or is it "fine" because Ruby 2.4 is EOL?

If we want to fix CI without dropping support, we'd have to add a restriction on the version of Rubocop in Gemfile.

@GustavoCaso GustavoCaso merged commit 37f01bd into master Apr 20, 2021
@GustavoCaso GustavoCaso deleted the bump-rubocop-ruby-target-version branch April 20, 2021 19:21
@shopify-shipit shopify-shipit bot temporarily deployed to rubygems April 20, 2021 19:23 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants