Skip to content

Drop support for Ruby 2.5 and 2.6#1578

Merged
andyw8 merged 4 commits into
masterfrom
andyw8/drop-support-for-ruby2.5-and-2.6
May 26, 2022
Merged

Drop support for Ruby 2.5 and 2.6#1578
andyw8 merged 4 commits into
masterfrom
andyw8/drop-support-for-ruby2.5-and-2.6

Conversation

@andyw8
Copy link
Copy Markdown
Contributor

@andyw8 andyw8 commented May 18, 2022

@jake-olney encountered an issue with RuboCop:

#1576

Upgrading rubocop-shopify solves it but it is not compatible with older Rubies.

@macournoyer suggested we should drop these as both are EOL: https://endoflife.date/ruby

@andyw8 andyw8 force-pushed the andyw8/drop-support-for-ruby2.5-and-2.6 branch from f1d75f2 to e6c0a2f Compare May 18, 2022 19:22
@andyw8 andyw8 force-pushed the andyw8/drop-support-for-ruby2.5-and-2.6 branch from e6c0a2f to 4ec0b85 Compare May 18, 2022 19:23
Comment thread Gemfile
end

group :test do
gem 'rubocop', '~> 1.4', require: false
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed this since rubocop is already a dependency of rubocop-shopify.

@andyw8 andyw8 marked this pull request as ready for review May 18, 2022 19:30
Copy link
Copy Markdown
Contributor

@macournoyer macournoyer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see no reasons to keep < 2.7 support around. @dylanahsmith do you know if we're using this anywhere w/ Ruby < 2.7?

Comment thread History.md Outdated
## 5.4.0 (unreleased)

### Breaking Changes
* Require Ruby >= 2.7 (#1578) [Andy Waite]
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Arguably this should be a major release (6.0), depending on how strict we're being with semver.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is already a "Changed" section with a potentially breaking change, so this should probably be combined with that section.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can move it, but I noticed the previous Ruby bump was listed under that section name:

### Breaking Changes
* Require Ruby >= 2.5 (#1131, #1310) [Mike Angell, Dylan Thacker-Smith]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I had called it "Changed" to de-emphasize the fact that it could break applications, since it wasn't clear that it would actually break applications in practice (the name "Changes" would have been more consistent with the other sections though).

I'm fine with calling it "Breaking Changes" and putting it first to further emphasize that this is dropping support for something, although perhaps it could be "Drop support for end-of-life ruby versions (2.5 & 2.6)" to again de-emphasize the scope of the breakage given that support for these versions has already been dropped upstream.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Updated in 3bbb7aa

@dylanahsmith
Copy link
Copy Markdown
Contributor

@macournoyer it shouldn't be a problem for us. It could affect users of the system version of ruby.

@andyw8 andyw8 merged commit d4c24f3 into master May 26, 2022
@andyw8 andyw8 deleted the andyw8/drop-support-for-ruby2.5-and-2.6 branch May 26, 2022 16:51
@andyw8 andyw8 mentioned this pull request May 26, 2022
@shopify-shipit shopify-shipit Bot temporarily deployed to rubygems July 29, 2022 14:31 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