Skip to content

[ruby] Update rubocop-rails 2.34.3 → 2.35.3 (minor)#2875

Open
depfu[bot] wants to merge 1 commit into
developfrom
depfu/update/rubocop-rails-2.35.3
Open

[ruby] Update rubocop-rails 2.34.3 → 2.35.3 (minor)#2875
depfu[bot] wants to merge 1 commit into
developfrom
depfu/update/rubocop-rails-2.35.3

Conversation

@depfu
Copy link
Copy Markdown
Contributor

@depfu depfu Bot commented Jun 6, 2026

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.34.3 → 2.35.3) · Repo · Changelog

Release Notes

2.35.3

Bug fixes

  • #1630: Fix a false positive in Rails/StrongParametersExpect when negating params[:key] with !, such as !params[:key]. (@koic)
  • #1629: Fix false positives in Rails/StrongParametersExpect when using the safe navigation operator (&.) on params[:key]. Autocorrecting params[:key]&.downcase to params.expect(:key).downcase silently changes behavior — a missing param goes from returning nil to raising ActionController::ParameterMissing. (@lucasmazza)

2.35.2

Bug fixes

  • #1625: Fix false positives in Rails/StrongParametersExpect when using collection methods (such as delete, keys, merge, slice, dig, fetch, or transform_values) on params[:key], as well as block-style calls such as params[:key].each { ... } or params[:key].map(&:to_s). (@koic)
  • #1627: Fix false positives in Rails/StrongParametersExpect for usages like params[:key].try(:method) and params[:key].try!(:method). (@nicholasdower)

2.35.1

Bug fixes

  • #1616: Fix false positives in Rails/StrongParametersExpect when using nil-safe conversion methods such as to_i, to_s, to_a, to_f, and to_h on params[:key]. (@koic)
  • #1622: Fix false positives in Rails/StrongParametersExpect when using key-check methods such as key?, has_key?, include?, and member? on params[:key]. (@koic)
  • #1620: Fix false positives in Rails/StrongParametersExpect when using type-check methods such as is_a?, kind_of?, and instance_of? on params[:key]. (@koic)

2.35.0

Bug fixes

  • #1595: Fix a false negative for Rails/I18nLocaleTexts when using redirect_back_or_to with a flash message. (@55728)
  • #1587: Fix false positives for Rails/Presence with operator methods like <<, =~, and others. (@eugeneius)
  • #1586: Don't add unnecessary parentheses in Rails/Presence. (@eugeneius)
  • #1602: Fix an error in Rails/SelectMap when .select appears inside a subquery in an argument. (@koic)
  • #1604: Allow DatabaseTypeResolvable to fall back to an adapter configuration specified in a shared key. (@codergeek121)
  • #1582: Fix a false negative where local was incorrectly treated as a known environment name when using == comparison in Rails/UnknownEnv. (@lovro-bikic)

Changes

  • #1571: Add more detection patterns on Rails/ResponseParsedBody. (@r7kamura)
  • #1583: Extend Rails/StrongParametersExpect to detect params[:key] in method calls and raising finder methods. (@koic)
  • #1584: Add support for case statements to Rails/UnknownEnv. (@lovro-bikic)
  • #1592: Fix false negative for != comparison in Rails/UnknownEnv. (@lovro-bikic)
  • #1598: Use glob patterns compatible with Engine or Packwerk for cops targeting spec/ and test/ directories. (@y-yagi)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 55 commits:

✳️ rubocop (1.86.2 → 1.87.0) · Repo · Changelog

Release Notes

1.87.0

New features

  • #15167: Add --enable-all-cops and --disable-all-cops command line options that override AllCops/EnabledByDefault and AllCops/DisabledByDefault in configuration files. (@koic)
  • #15185: Make Layout/EmptyLineAfterGuardClause accept the new # simplecov:disable and # simplecov:enable directive comments. (@koic)
  • #15173: Add optional Rubydex integration via AllCops/UseProjectIndex to enable cross-file detection in Lint/ConstantReassignment (experimental). (@koic)

Bug fixes

  • #15168: Fix false positives in Lint/ParenthesesAsGroupedExpression when the first argument is a call-like expression with its own parentheses, such as yield(...). (@koic)
  • #15188: Fix false positives in Style/YodaCondition when one side is an array or hash literal containing non-literal elements. (@koic)
  • #15182: Fix incorrect autocorrect for Style/Alias causing a syntax error when the return value of alias_method is used, such as an argument to public, private, protected, or module_function, or the right-hand side of an assignment. (@koic)
  • #15174: Fix incorrect autocorrect for Style/ClassAndModuleChildren causing a syntax error when the namespace contains a method call (e.g., class self.class::Foo; end). (@koic)
  • #15180: Fix incorrect autocorrect for Style/FileWrite causing a syntax error when the written heredoc is chained with another method call. (@koic)
  • #15186: Fix incorrect autocorrect for Style/HashConversion causing a syntax error when Hash[...] is passed an anonymous splat (*). (@koic)
  • #15192: Fix incorrect autocorrect for Style/StructInheritance causing a syntax error when the inherited Struct.new is called without parentheses. (@koic)
  • #15170: Fix an infinite loop for Layout/RedundantLineBreak when a single-line block is chained with a safe navigation method call. (@koic)
  • #15175: Fix Layout/IndentationWidth to indent block bodies relative to the method selector for trailing-dot multi-line method chains when EnforcedStyleAlignWith is relative_to_receiver. (@ddbrendan)
  • #15135: Fix incorrect autocorrect for Style/RedundantParentheses that swallowed chained method calls into a trailing inline comment on the line above the closing parenthesis. (@hammadxcm)
  • #15184: Fix various typos and grammar mistakes in documentation and cop descriptions. (@bbatsov)

Changes

  • #15171: Cache FilePatterns#match? results per path so cops sharing the same Include/Exclude configuration do not each repeat File.fnmatch? work on every file. (@Darhazer)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 29 commits:

↗️ json (indirect, 2.19.5 → 2.19.8) · Repo · Changelog

Release Notes

2.19.8 (from changelog)

  • Fix 1-byte buffer overread on EOS errors.
  • Handle invalid types passed as max_nesting option.

2.19.7

What's Changed

  • Fix some more edge cases with out of range floats.
  • Ensure the string provided to JSON.parse can't be mutated during parsing.
  • Add missing write barriers in State#dup.
  • Further validate generator depth config.

Full Changelog: v2.19.6...v2.19.7

2.19.6

What's Changed

  • Cleanly handle overly large depth generator argument.
  • Add missing write barrier in ParserConfig.

Full Changelog: v2.19.5...v2.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:


Depfu Status

Depfu 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
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu Bot added the dependencies Pull requests that update a dependency file label Jun 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants