Skip to content

Remove misleading RuboCop comment in gemspec#403

Open
tagliala wants to merge 1 commit into
roidrage:masterfrom
tagliala:chore/remove-confusing-rubocop-comment
Open

Remove misleading RuboCop comment in gemspec#403
tagliala wants to merge 1 commit into
roidrage:masterfrom
tagliala:chore/remove-confusing-rubocop-comment

Conversation

@tagliala

Copy link
Copy Markdown

The comment claimed Ruby 2.5 was the oldest syntax supported by RuboCop, but this was only true briefly in RuboCop 1.28 (Apr 2022) when runtime and code analysis support were accidentally dropped together.

RuboCop quickly restored code analysis support:

RuboCop now supports analyzing Ruby 2.0+ code, so the comment is misleading and should be removed.

The gem's minimum Ruby version is a project-level decision best guided by its own compatibility goals rather than by the support matrix of any single development tool. With Ruby 3.2 being the current minimum non-EOL release, >= 2.5 already offers generous backward compatibility.

The comment claimed Ruby 2.5 was the oldest syntax supported by
RuboCop, but this was only true briefly in RuboCop 1.28 (Apr 2022)
when runtime and code analysis support were accidentally dropped
together.

RuboCop quickly restored code analysis support:
- PR rubocop/rubocop#10626 (May 12 2022 v1.29.1) restored TargetRubyVersion 2.5
- PR rubocop/rubocop#10668 (May 25 2022) restored TargetRubyVersion 2.0

RuboCop now supports analyzing Ruby 2.0+ code, so the comment is
misleading and should be removed.

The gem's minimum Ruby version is a project-level decision best
guided by its own compatibility goals rather than by the support
matrix of any single development tool. With Ruby 3.2 being the
current minimum non-EOL release, >= 2.5 already offers generous
backward compatibility.
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