Upgrade to Ruby 3.1 #1114
Closed
Upgrade to Ruby 3.1 #1114
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In order to know if we have any deprecation warnings in version 2.7, we need to update to the latest version.
In order to get to version 3.1, we want to first move to version 3.0 to ensure that it's working as expected, as well as there are no deprecation warnings.
Update ruby to the final current version of 3.1
As we are upgrading our ruby version, there are dependencies that need to be updated as well to ensure that their are behaving as expected. The following gems were updated: - `bundler`: v2.2.33 doesn't work well with ruby v3.1 and shows the following warning: - `Calling 'DidYouMean::SPELL_CHECKERS.merge!(error_name => spell_checker)' has been deprecated. Please call 'DidYouMean.correct_error(error_name, spell_checker)' instead. - `contracts`: according to the warning during bundling, v0.16 should be used only with ruby v2.x. For ruby v3.x +, we should use v0.17 - `cucumber`: v2.0 has some warnings about redefining methods that already exists in the gem.
To make sure that our bundling will work as expected, we should use the same version we current have in the CI, v2.3.26
Closed
|
I didn't find any of these changes necessary either locally or in #1117 |
|
#1117 Passed and has been merged so I don't think these changes are necessary. Closing this but please reopen if I've misunderstood something |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Ruby 2.7 is reaching its end-of-life in March 2023. To ensure that we are working with up-to-date versions that receive security updates, we are upgrading our ruby version to 3.1.
As we are upgrading our ruby version, dependencies need to be updated to ensure that they are behaving as expected.
The following gems were updated/version-locked:
bundler: v2.2.33 doesn't work well with ruby v3.1 and shows the following warning whenever bundler is called. For that reason, we are using the exact same version as the CI, v2.3.26:contracts: according to the warning during bundling, v0.16 should be used only with ruby v2.x. For ruby v3.x +, we should use v0.17cucumber: v2.0 has warnings about redefining methods within the gem. So we are using v8.0