Skip to content

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Dec 4, 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?

✳️ yabeda-rails (0.10.0 → 0.11.0) · Repo · Changelog

Release Notes

0.11.0

Added

  • Ability to use procs and regexps in ignore_actions configuration. [@lewispb][] in #34, [@Envek][]

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

Commits

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

↗️ dry-initializer (indirect, 3.0.4 → 3.2.0) · Repo · Changelog

Release Notes

3.2.0

Changed

  • Set minimal supported Ruby version to 3.1 (@flash-gordon)
  • Exclude block forwarding from Root#initialize. This helps
    with tracking down calls that shouldn't pass a block in Ruby 3.4 (see #109) (@flash-gordon)

Compare v3.1.1...v3.2.0

3.1.1

Changed

  • Improved error messages were rolled back, they created an implicit dependency on dry-types (@flash-gordon)

Compare v3.1.0...v3.1.1

3.1.0

Changed

  • Improved error messages on type mismatch (@swerling)
  • [BREAKING] Minimal supported Ruby version is 2.7 (@flash-gordon)

Compare v3.0.4...v3.1.0

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ rack (indirect, 2.2.20 → 2.2.21) · Repo · Changelog

Release Notes

2.2.21 (from changelog)

Fixed

  • Multipart parser: limit MIME header size check to the unread buffer region to avoid false multipart mime part header too large errors when previously read data accumulates in the scan buffer. (#2392, @alpaca-tc, @willnet, @krororo)

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

Commits

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

↗️ rake (indirect, 13.3.0 → 13.3.1) · Repo · Changelog

Release Notes

13.3.1

What's Changed

  • Remove useless condition check by @DormancyWang in #636
  • Added document for RAKEOPT by @hsbt in #639
  • lewagon/wait-on-check-action didn't need bot token by @hsbt in #642
  • Fixed wrong name of environmental variable by @hsbt in #643
  • The old Ruby version of Windows is broken by @hsbt in #647
  • Avoid to use it by @hsbt in #650
  • Fixed assertion result with the latest stable version of JRuby by @hsbt in #655
  • Fixup test_load_error_raised_implicitly with JRuby by @hsbt in #657
  • Set source_code_uri metadata to this gem's public repo URL by @amatsuda in #662
  • Fix TaskArguments#deconstruct_keys with keys = nil by @nevans in #635
  • refactor: only include lib in $LOAD_PATH if not included yet by @pvdb in #610
  • silence warnings during execution of rake tasks in Rakefile (ex: rake test) by @luke-gru in #483

New Contributors

Full Changelog: v13.3.0...v13.3.1

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

Commits

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

↗️ zeitwerk (indirect, 2.6.15 → 2.7.3) · Repo · Changelog

Release Notes

2.7.3 (from changelog)

  • The helper Zeitwerk::Loader#cpath_expected_at did not work correctly if the inflector had logic that relied on the absolute path of the given file or directory. This has been fixed.

    This bug was found by Codex.

  • Perpetual internal work.

2.7.2 (from changelog)

  • Internal improvements and micro-optimizations.

  • Add stable TruffleRuby to CI.

2.7.1 (from changelog)

  • Micro-optimization in a hot path.

  • Raises Zeitwerk::Error if an autoloaded constant expected to represent a namespace does not store a class or module object.

  • Adds truffleruby-head to CI, except for autoloading thread-safety (see why in oracle/truffleruby#2431).

2.7.0 (from changelog)

  • Explicit namespaces can now also be defined using constant assignments.

    While constant assignments like

    # coordinates.rb

    Coordinates = Data.define(:x, :y)

    worked for most objects, they did not for classes and modules that were also namespaces (i.e., those defined by a file and matching subdirectories). In such cases, their child constants could not be autoloaded.

    This limitation has been removed.

  • TracePoint is no longer used.

  • Requires Ruby 3.2 or later.

    Gems that work with previous versions of Zeitwerk also work with this one. If they support Ruby versions older than 3.2 they can specify a relaxed version constraint for Zeitwerk like "~> 2.6", for example.

    In client projects, Bundler takes the Ruby requirement into account when resolving dependencies, so Gemfile.lock will get one compatible with the Ruby version being used.

2.6.18 (from changelog)

  • Fixes a bug in which projects reopening the main namespace of a gem dependency managed by its own Zeitwerk loader could not reload the constants they added to that external namespace.

2.6.17 (from changelog)

  • Fix log message when eager loading a directory ends.

2.6.16 (from changelog)

  • Logging prints a message when a directory that was not ignored is skipped anyway because it contains no Ruby files.

  • Internal refactors.

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.


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 4, 2025
@digitaltom digitaltom added the 2.25 label Dec 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants