Drop support for Ruby 2.5

[mvz]

Summary

Drop support for Ruby 2.5

Details

• Require Ruby 2.6 or higher in the gemspec
• Update RuboCop configuration and fix new offenses
• Update set of Rubies in CI

Motivation and Context

With the release of JRuby 9.3.0.0, we can drop compatibility with Ruby 2.5. MRI 2.5 has been unmaintained for a while now.

How Has This Been Tested?

CI

Types of changes

This is a potentially breaking change for versions of rubygems and bundler that do not take ruby version requirements into account. From the standpoint of semver, it is not a breaking API change so does not require a major version bump.

Checklist:

• [ ] I've added tests for my code
• [x] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.

[mvz]

I'm going to delay this until cucumber itself drops support for 2.5.

[mvz]

Cucumber 8 has dropped support for Ruby 2.5. I'm first going to release a version with cucumber 8 support. After that, I'm going to revisit this pull request.

[mvz]

It seems there's a consistent test failure with Ruby 3.1 on Windows that is only now coming to light because this pull request adds Ruby 3.1 to the matrix on Windows.

The failure messages point to ChildProcess, but that project is not up-to-date on test environments so it's hard to tell whether Aruba is doing something wrong that only comes to light in that combination, or there's a problem with the combination of ChildProcess, Ruby 3.1 and Windows.

[mvz]

I dropped 3.1 from the Windows build set for now.