Update rubocop-rails 2.35.0 → 2.35.3 (patch)#1900
Merged
Merged
Conversation
hennevogel
approved these changes
Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rubocop-rails (2.35.0 → 2.35.3) · Repo · Changelog
Release Notes
2.35.3
2.35.2
2.35.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 24 commits:
Cut 2.35.3Update ChangelogMerge pull request #1631 from koic/fix_false_positive_for_rails_strong_parameters_expect_with_negation[Fix #1630] Fix a false positive in `Rails/StrongParametersExpect`Merge pull request #1629 from lucasmazza/fix/strong-parameters-expect-safe-navigationFix Rails/StrongParametersExpect to allow safe navigation operator on optional paramsReset the docs versionCut 2.35.2Update ChangelogMerge pull request #1626 from koic/fix_false_positives_for_rails_strong_parameters_expect_with_collection_methods[Fix #1625] Fix false positives in `Rails/StrongParametersExpect`Merge pull request #1627 from nicholasdower/tryFix false positives for try and try! in Rails/StrongParametersExpectReset the docs versionCut 2.35.1Update ChangelogMerge pull request #1624 from koic/fix_false_positives_for_rails_strong_parameters_expect_with_key_check_methods[Fix #1622] Fix false positives in `Rails/StrongParametersExpect`Merge pull request #1623 from koic/fix_false_positives_for_rails_strong_parameters_expect_with_type_check_methods[Fix #1620] Fix false positives in `Rails/StrongParametersExpect`Merge pull request #1616 from koic/fix_false_positives_in_rails_strong_parameters_expect[Fix #1618] Update the doc of `Rails/RedundantActiveRecordAllMethod`Fix false positives in `Rails/StrongParametersExpect`Reset the docs version✳️ rubocop (1.86.2 → 1.87.0) · Repo · Changelog
Release Notes
1.87.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 29 commits:
Cut 1.87Update ChangelogFix incorrect autocorrect for `Style/StructInheritance` cop[Fix #15185] Make `Layout/EmptyLineAfterGuardClause` accept new SimpleCov directivesMerge pull request #15190 from koic/fix_false_positives_in_style_yoda_condition[Fix #15188] Fix false positives for `Style/YodaCondition`Fix incorrect autocorrect for `Style/HashConversion` copMerge pull request #15184 from rubocop/fix-typos-and-grammar-in-docsFix various typos and grammar mistakes in documentationMerge pull request #15182 from koic/fix_incorrect_autocorrect_for_style_alias_inside_visibility_modifierFix incorrect autocorrect for `Style/Alias` copMerge pull request #15180 from koic/fix_incorrect_autocorrect_for_style_file_write_copFix incorrect autocorrect for `Style/FileWrite` copAdd lazy load support to RegistryAdd `--enable-all-cops` and `--disable-all-cops` command line optionsAdd optional Rubydex integrationMerge pull request #15175 from ddbrendan/fix/multiline-block-body-indentation-after-chainMerge pull request #15174 from koic/fix_incorrect_autocorrect_for_style_class_and_module_childrenFix `Layout/IndentationWidth` for trailing-dot chains under `relative_to_receiver`Fix incorrect autocorrect for `Style/ClassAndModuleChildren`Merge pull request #15140 from hammadxcm/fix/15135-redundant-parentheses-comment-swallows-chainMerge pull request #15171 from rubocop/cache-file-patterns-match-resultsCache `FilePatterns#match?` results per pathMerge pull request #15170 from koic/fix_infinite_loop_for_layout_redundant_line_breakFix an infinite loop for `Layout/RedundantLineBreak` copMerge pull request #15169 from koic/fix_false_positives_in_lint_parentheses_as_grouped_expression[Fix #15168] Fix false positives in `Lint/ParenthesesAsGroupedExpression`Use mcp gem 0.16.0+ for developmentReset the docs versionRelease Notes
2.19.8 (from changelog)
2.19.7
2.19.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
Release 2.19.8Prevent buffer over-read when generating EOF errorHandle invalid types passed as `max_nesting` optionGet rid of all_images gemAdd a security note in READMERelease 2.19.7Fix some more edge cases with out of range floatsparser.c: Ensure the user provided string can't be mutatedgenerator.c: trigger write barriers in cState_init_copyFurther validate generator `depth` configRelease 2.19.6Add ruby-asan to CIgenerator.c: Handle stupidly large depthAdd missing write barrier in ParserConfigDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands