Skip to content

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Dec 14, 2025

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.0 → 2.34.2) · Repo · Changelog

Release Notes

2.34.2

Changes

  • #1565: Make Rails/Presence allow index access methods. (@koic)

2.34.1

Bug fixes

  • #1556: Fix an error for Rails/Env when assigning Rails.env. (@koic)
  • #1557: Fix false positives for Rails/Presence with comparison and assignment operators. (@davidenglishmusic)
  • #1558: This PR fixes incorrect autocorrect for Rails/RedirectBackOrTo when additional options as double splat are used. (@koic)
  • #1561: Fix incorrect autocorrect for Rails/RedirectBackOrTo when fallback_location argument is a hash and the call has no argument parentheses. (@koic)

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

Commits

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

↗️ concurrent-ruby (indirect, 1.3.5 → 1.3.6) · Repo · Changelog

Commits

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

↗️ connection_pool (indirect, 2.5.4 → 3.0.2) · Repo · Changelog

Release Notes

3.0.2 (from changelog)

  • Support :name keyword for backwards compatibility [#210]

3.0.1 (from changelog)

  • Add missing fork.rb to gemspec.

3.0.0 (from changelog)

  • BREAKING CHANGES ConnectionPool and ConnectionPool::TimedStack now use keyword arguments rather than positional arguments everywhere. Expected impact is minimal as most people use the with API, which is unchanged.
pool = ConnectionPool.new(size: 5, timeout: 5)
pool.checkout(1) # 2.x
pool.reap(30)    # 2.x
pool.checkout(timeout: 1) # 3.x
pool.reap(idle_seconds: 30) # 3.x
  • Dropped support for Ruby <3.2.0

2.5.5 (from changelog)

  • Support ConnectionPool::TimedStack#pop(exception: false) [#207] to avoid using exceptions as control flow.

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

Commits

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

↗️ json (indirect, 2.16.0 → 2.18.0) · Repo · Changelog

Release Notes

2.18.0

What's Changed

  • Add :allow_control_characters parser options, to allow JSON strings containing unescaped ASCII control characters (e.g. newlines).

Full Changelog: v2.17.1...v2.18.0

2.17.1 (from changelog)

  • Fix a regression in parsing of unicode surogate pairs (\uXX\uXX) that could cause an invalid string to be returned.

2.17.0

What's Changed

  • Improve JSON.load and JSON.unsafe_load to allow passing options as second argument.
  • Fix the parser to no longer ignore invalid escapes in strings.
    Only \", \\, \b, \f, \n, \r, \t and \u are valid JSON escapes.
  • Fixed JSON::Coder to use the depth it was initialized with.
  • On TruffleRuby, fix the generator to not call to_json on the return value of as_json for Float::NAN.
  • Fixed handling of state.depth: when to_json changes state.depth but does not restore it, it is reset
    automatically to its initial value.
    In particular, when a NestingError is raised, depth is no longer equal to max_nesting after the call to
    generate, and is reset to its initial value. Similarly when to_json raises an exception.

Full Changelog: v2.16.0...v2.17.0

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

Commits

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

↗️ minitest (indirect, 5.26.2 → 5.27.0) · Repo · Changelog

Release Notes

5.27.0 (from changelog)

  • 1 major enhancement:

    • Adding post install message announcing the EOL for minitest 5!

  • 2 minor enhancements:

    • Removed TestTask::Work#initialize since Queue can now initialize with an Enumerable! AMAZING!

    • Use Kernel#warn uplevel argument for nicer warnings. (byroot)

  • 5 bug fixes:

    • Cleaned up option aliasing a tad.

    • Removed obsolete conditional for prerecord

    • Removed obsolete guards around Warning.

    • Removed obsolete version guards for pattern matching assertions.

    • Switched all internal requires to require_relative.

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

Commits

See the full diff on Github. The new version differs by 15 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 depfu label Dec 14, 2025
@danidoni danidoni force-pushed the depfu/update/rubocop-rails-2.34.2 branch from 2e745d4 to 30bccf5 Compare December 15, 2025 11:10
@danidoni
Copy link
Contributor

Updated with --conservative instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants