Skip to content

Fix RuboCop deprecation warnings#641

Closed
mattmenefee wants to merge 1 commit intosds:mainfrom
mattmenefee:fix-rubocop-deprecation-warnings
Closed

Fix RuboCop deprecation warnings#641
mattmenefee wants to merge 1 commit intosds:mainfrom
mattmenefee:fix-rubocop-deprecation-warnings

Conversation

@mattmenefee
Copy link
Copy Markdown
Contributor

Summary

  • Switch require: rubocop-performance to plugins: rubocop-performance per RuboCop's new plugin system
  • Rename Naming/PredicateName cop to Naming/PredicatePrefix to match the upstream rename

Test plan

  • bundle exec rubocop runs clean with no warnings and no offenses

- Use `plugins` instead of `require` for rubocop-performance, per the
  new plugin system
- Rename `Naming/PredicateName` to `Naming/PredicatePrefix` to match
  the upstream cop rename
@mattmenefee
Copy link
Copy Markdown
Contributor Author

Closing — these config changes break backward compatibility with RuboCop 1.0.x, which is still in the supported version range (gemspec requires >= 1.0). The old names produce harmless deprecation warnings in newer RuboCop but the new names cause hard errors in RuboCop 1.0.

@mattmenefee mattmenefee closed this Apr 8, 2026
@mattmenefee mattmenefee deleted the fix-rubocop-deprecation-warnings branch April 8, 2026 20:24
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