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

Recover Ruby 2.0 code analysis using TargetRubyVersion: 2.0 #10668

Merged
merged 1 commit into from May 25, 2022

Conversation

koic
Copy link
Member

@koic koic commented May 25, 2022

Follow up #10632 (comment).

Reverts part of #4787.

Only the Ruby version (2.0) to runtime should have been dropped, not code analysis.
This PR makes Ruby 2.0 code analysis with TargetRubyVersion: 2.0.
It aims to solve essentially the same problem as #10626, #10632, #10640, #10644, and #10662.


Before submitting the PR make sure the following are checked:

  • The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
  • Wrote good commit messages.
  • Commit message starts with [Fix #issue-number] (if the related issue exists).
  • Feature branch is up-to-date with master (if not - rebase it).
  • Squashed related commits together.
  • Added tests.
  • Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
  • Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Follow up rubocop#10632 (comment).

Reverts part of rubocop#4787.

Only the Ruby version (2.0) to runtime should have been dropped, not code analysis.
This PR makes Ruby 2.0 code analysis with `TargetRubyVersion: 2.0`.
It aims to solve essentially the same problem as rubocop#10626, rubocop#10632, rubocop#10640, rubocop#10644, and rubocop#10662.
@bbatsov bbatsov merged commit a4c197c into rubocop:master May 25, 2022
@bbatsov
Copy link
Collaborator

bbatsov commented May 25, 2022

Thanks!

@koic koic deleted the recover_ruby_20 branch May 25, 2022 11:54
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.

None yet

2 participants