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

Add Ruby 3.2 to test matrix & use it in development #136

Merged
merged 2 commits into from
Feb 3, 2023
Merged

Conversation

sambostock
Copy link
Contributor

This adds Ruby 3.2 to the test matrix & uses it in development. This doesn't change anything else. RuboCop remains configured to enforce 2.5 compatible syntax.

We test other versions in CI, so there's no reason not use the latest
and greatest locally.
@sambostock sambostock requested a review from a team as a code owner February 3, 2023 16:56
@@ -11,7 +11,7 @@ jobs:
strategy:
fail-fast: false
matrix:
ruby: [ '2.5', '2.6', '2.7', '3.0', '3.1' ]
ruby: [ '2.5', '2.6', '2.7', '3.0', '3.1', '3.2' ]
Copy link
Contributor

Choose a reason for hiding this comment

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

I wonder if we should drop 2.5 and 2.6.

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was just creating a "we should publish 1.0" issue, in which I was going to recommend that be when we drop old Ruby versions, and switch to the new RuboCop APIs.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The upcoming end-of-life of Ruby 2.7 might be a good time to drop everything older than Ruby 3, although that might be a little aggressive.

@sambostock sambostock merged commit 38eeb8c into main Feb 3, 2023
@sambostock sambostock deleted the ruby-3-2 branch February 3, 2023 20:22
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