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

Update Rubocop to TargetRubyVersion 2.3 #2311

Merged
merged 1 commit into from
Nov 16, 2017

Conversation

adamleff
Copy link
Contributor

Bumps the Rubocop engine to use 2.3 and addresses the big changes between 2.0 and 2.3.

Bumps the Rubocop engine to use 2.3 and addresses the big changes
between 2.0 and 2.3.

Signed-off-by: Adam Leff <[email protected]>
@adamleff adamleff requested a review from a team as a code owner November 16, 2017 16:18
@adamleff adamleff merged commit dde4a11 into master Nov 16, 2017
@adamleff adamleff deleted the adamleff/rubocop-2.3-updates branch November 16, 2017 16:26
adamleff added a commit that referenced this pull request Nov 16, 2017
PR #2311 updated the Rubocop engine to use Ruby 2.3 to evaluate, and
the default behavior is to no longer require `.freeze` to be added
to string literals that are treated like constants. This caused the
pattern match used in the Expeditor version update script to no longer
work.

Also manually fixing the `lib/inspec/version.rb` file to be correct.

Signed-off-by: Adam Leff <[email protected]>
adamleff added a commit that referenced this pull request Nov 16, 2017
PR #2311 updated the Rubocop engine to use Ruby 2.3 to evaluate, and
the default behavior is to no longer require `.freeze` to be added
to string literals that are treated like constants. This caused the
pattern match used in the Expeditor version update script to no longer
work.

Also manually fixing the `lib/inspec/version.rb` file to be correct.

Signed-off-by: Adam Leff <[email protected]>
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.

1 participant