-
Notifications
You must be signed in to change notification settings - Fork 25
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
Fix RuboCop warnings and default Ruby version #288
Conversation
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.
The changes make sense to me, I have one question about dependents outside of GitHub.
url: url, | ||
read_timeout: read_timeout, | ||
open_timeout: open_timeout, | ||
url:, | ||
read_timeout:, | ||
open_timeout:, |
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.
yay, i love seeing this shorthand ❤️
ruby-version: ['3.0', '3.1', '3.2'] | ||
ruby-version: ['3.2'] | ||
ES_VERSION: ['5.6.15', '8.7.0'] | ||
include: | ||
- ES_VERSION: '5.6.15' |
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.
Does this mean that we're no longer supporting 3.0 or 3.1 at all with elastomer client? Will that cause any customer impact, if users are depending upon that support?
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.
Yeah, since the library is only used internally, we're focusing support on the version we run.
This PR takes parts of another PR to focus on just the RuboCop fixes needed to get RuboCop in CI working.
.ruby-version
to the latest availablebundle exec rubocop -a
).