Upgrade version of ruby from 3.3.0 => 3.3.7 #1449
Merged
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.
Currently the
reek
plugin is failing for customers. The stack trace for these customers looks like this:Initially this was very confusing since there were no CLI upgrades between when it was working and when it suddenly stopped working ...
In digging into it, we discovered that:
~1.8
Because of the dependency chain, this upgrade was picked up and changed the behavior of the plugin.
The upgrade apparently exposed a bug in Ruby 3.3.0 that it previously hadn't run into. (h/t dry-rb/dry-system#284 (comment)).
This PR bumps the version of ruby to the latest on the 3.3.x line (
3.3.7
).However, I'm currently unable to install this locally via qlty and cannot verify that it does indeed fix the bug.
Reek
runs tests on 3.3.6, so that is also a fairly safe alternative (but also does not install locally for me).