-
-
Notifications
You must be signed in to change notification settings - Fork 504
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
Upgrade to Ruby 3.2 #3950
Upgrade to Ruby 3.2 #3950
Conversation
@@ -5,8 +5,6 @@ git_source(:github) do |repo_name| | |||
"https://github.com/#{repo_name}.git" | |||
end | |||
|
|||
ruby "3.1.2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this deleted by mistake? bundler
needs to know the ruby version.
Is there a hook within the project for the bundler to read from .ruby-version
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it's not a mistake - Cloud66 [explicitly says to delete this](https://help.cloud66.com/docs/build-and-config/managing-and-upgrading-ruby-versions#how-we-determine-the-version-to-use). It's not needed within the Gemfile. If you're using a Ruby version manager like RVM or asdf, it'll use .ruby-version
. We control the version on CI with our GitHub Actions file, and Cloud66 uses the manifest file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha! And @dorner have you noticed any issue with this in local development? ( I like the code when it is more explicit than implicit. ) Cloud66
checks the version in manifest
file first. So we can have it in both the places to satisfy local dev & deployment. Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, haven't noticed any issue. I left in .ruby-version
which would power local dev.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I was going to ask for .tool-versions to be updated too, but then realized that is local only right now :)
@dorner: Your PR |
No description provided.