[ruby] Update rubocop-rails 2.35.0 → 2.35.3 (patch)

[depfu]

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

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)

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.3
• Update Changelog
• Merge 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-navigation
• Fix Rails/StrongParametersExpect to allow safe navigation operator on optional params
• Reset the docs version
• Cut 2.35.2
• Update Changelog
• Merge 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/try
• Fix false positives for try and try! in Rails/StrongParametersExpect
• Reset the docs version
• Cut 2.35.1
• Update Changelog
• Merge 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

↗️ 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:

• Release 2.19.8
• Prevent buffer over-read when generating EOF error
• Handle invalid types passed as `max_nesting` option
• Get rid of all_images gem
• Add a security note in README
• Release 2.19.7
• Fix some more edge cases with out of range floats
• parser.c: Ensure the user provided string can't be mutated
• generator.c: trigger write barriers in cState_init_copy
• Further validate generator `depth` config
• Release 2.19.6
• Add ruby-asan to CI
• generator.c: Handle stupidly large depth
• Add missing write barrier in ParserConfig

---

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)