Skip to content
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 for Ruby 3.0, and adopt Rubycritic changes for Ruby 3.1. #492

Merged
merged 1 commit into from
Dec 2, 2024

Conversation

faisal
Copy link
Contributor

@faisal faisal commented Jun 7, 2024

While we have not yet dropped support for Ruby 2.7 (EOL'd over a year ago), Ruby 3.0 EOL'd a couple months ago and this PR does the work to move forward from there.

  • Drop support for Ruby 3.0.
  • Update Rubycritic config to target Ruby 3.1. Apply all safe autocorrections except for Style/HashSyntax.
  • Set Rubycritic's Style/HashSyntax EnforcedShorthandSyntax to 'never', which keeps the old style in place (and consistent) until we decide to convert.
  • Add Ruby 3.3 to the test matrix and Drop Ruby 3.0.
  • Bump minitest, mocha, rubocop dependencies

Check list:

@faisal
Copy link
Contributor Author

faisal commented Jun 7, 2024

@etagwerker @nunosilva800 Regarding Rubocop's preference EnforcedShorthandSyntax, I set that to either so as to minimize the change in this PR. Another option would be to adopt that default setting, and let rubocop -a do the safe right thing. What do you think makes sense here?

- Drop support for Ruby 3.0.
- Update Rubycritic config to target Ruby 3.1. Apply all safe autocorrections except for Style/HashSyntax.
- Set Rubycritic's Style/HashSyntax EnforcedShorthandSyntax to 'never', which keeps the old style in place (and consistent) until we decide to convert.
- Add Ruby 3.3 to the test matrix and Drop Ruby 3.0 (which largely includes the changes in whitesmith#488, so we'll need to rebase if that's landed when we do something with this)
- Bump minitest, mocha, rubocop dependencies
@faisal
Copy link
Contributor Author

faisal commented Dec 1, 2024

The failure in 3.4 seems to be an issue with running cucumber on ruby 3.4-dev, and unrelated to this project. I can reproduce it elsewhere, even on null projects.

@faisal
Copy link
Contributor Author

faisal commented Dec 1, 2024

cucumber/cucumber-ruby#1769

This is fixed in main - It will be released in cucumber v10. For now if you stick to ruby 3.3 you should be fine

Copy link
Collaborator

@etagwerker etagwerker left a comment

Choose a reason for hiding this comment

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

@faisal Looks good to me, thank you! 🙏🏼

@etagwerker etagwerker merged commit 88439e6 into whitesmith:main Dec 2, 2024
21 of 22 checks passed
@faisal faisal deleted the ruby_31 branch December 3, 2024 00:38
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.

2 participants