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

• build(bump): bump to version 0.10.16
• Merge pull request #2495 from janko/fix-global-config
• Fix changing config in subclass having global effect
• Merge pull request #2492 from StreetIQ/rails_81_warnings
• Remove use of ActiveSupport::Configurable
• Bring back few old ruby/rails matrix to CI
• Add Ruby 3.4 and Rails 8.1 to CI matrix
• Fix minitest assertion for Ruby >= 3.4
• Add mutex_m to Gemfile for Ruby >= 3.4
• Add ostruct to Gemfile for Ruby >= 3.4
• Require 'logger'
• Pin json version to < 2.10

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.

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

• Bump patch version.
• Allow Multipart head to span read boundary. (#2392)

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.

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

@​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)