🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
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.
There is a possible DoS vulnerability in the model name parsing section
of the GlobalID gem. Carefully crafted input can cause the regular
expression engine to take an unexpected amount of time. All users running
an affected release should either upgrade or use one of the workarounds
immediately.
Possible ReDoS based DoS vulnerability in GlobalID
There is a ReDoS based DoS vulnerability in the GlobalID gem. This
vulnerability has been assigned the CVE identifier CVE-2023-22799.
Versions Affected: >= 0.2.1
Not affected: NOTAFFECTED
Fixed Versions: 1.0.1
Impact
There is a possible DoS vulnerability in the model name parsing section of the
GlobalID gem. Carefully crafted input can cause the regular expression engine
to take an unexpected amount of time. All users running an affected release
should either upgrade or use one of the workarounds immediately.
Releases
The FIXED releases are available at the normal locations.
Changed DateTime results to always use the proleptic Gregorian calendar. This affects DateTime results prior to 1582-10-15 and any arithmetic performed on the results that would produce a secondary result prior to 1582-10-15.
Added support for eager loading all the time zone and country data by calling either TZInfo::DataSource#eager_load! or TZInfo.eager_load!. Compatible with Ruby On Rails' eager_load_namespaces. #129.
Ignore the SECURITY file from Arch Linux's tzdata package. #134.
If an autoload is triggered, the file is loaded successfully, but the expected
constant does not get defined, Ruby resets the state of the module. In
particular, autoload? returns nil for that constant name, and constants
does not include the constant name (starting with Ruby 3.1).
Zeitwerk is more strict, not defining the expected constant is an error
condition and the loader raises Zeitwerk::NameError. But this happens during
the require call and the exception prevents Ruby from doing that cleanup.
With this change, the parent module is left in a state that makes more sense
and is consistent with what Ruby does.
A message is logged if an autoload did not define the expected constant.
When that happens, Zeitwerk::NameError is raised and you normally see the
exception. But if the error is shallowed, and you are inspecting the logs to
investigate something, this new message may be helpful.
By default, Zeitwerk::Loader#dirs filters ignored root directories out.
Please, pass ignored: true if you want them included.
It is very strange to configure a root directory and also ignore it, the edge
case is supported only for completeness. However, in that case, client code
listing root directories rarely needs the ignored ones.
Documentation improvements.
Enforcement of private interfaces continues with another gradual patch.
2.6.6 (from changelog)
The new eager_load_namespace had a bug when eager loading certain namespaces
with collapsed directories. This has been fixed.
2.6.5 (from changelog)
Controlled errors in a couple of situations:
Attempting to eager load or reload without previously invoking setup now
raises Zeitwerk::SetupRequired.
The method Zeitwerk::Loader#push_dir raises Zeitwerk::Error if it gets
an anonymous custom namespace.
These should be backwards compatible, because they raise in circumstances that
didn't work anyway. The goal here is to provide a meaningful error upfront.
Enforcement of private interfaces continues with another gradual patch.
2.6.4 (from changelog)
Ruby does not have gem-level visibility, so sometimes you need things to be
public for them to be accessible internally. But they do not belong to the
public interface of the gem.
A method that is undocumented and marked as @private in the source code is
clearly private API, regardless of its formal Ruby visibility.
This release starts a series of gradual patches in which private interface is
enforced with stricter formal visibility.
2.6.3 (from changelog)
v2.6.2 introduced a regression in the logic that checks whether two loaders
want to manage the same root directories. It has been fixed.
2.6.2 (from changelog)
Zeitwerk::Loader#load_file allows you to load an individual Ruby file. Check
its documentation
for details.
Zeitwerk::Loader#eager_load_dir allows you to eager load a directory,
recursively. Check its
documentation for
details.
Zeitwerk::Loader#eager_load_namespace allows you to eager a namespace,
recursively. Namespaces are global, this method loads only what the receiver
manages from that namespace, if anything. Check its
documentation for
details.
Zeitwerk::Loader.eager_load_namespace broadcasts eager_load_namespace to
all registered loaders. Check its
documentation
for details.
Documents shadowed files.
They always existed, but were not covered by the documentation.
Other assorted documentation improvements.
2.6.1 (from changelog)
Zeitwerk::Loader#dirs allows you to instrospect the root directories
configured in the receiver. Please check its
documentation for details.
2.6.0 (from changelog)
Directories are processed in lexicographic order.
Different file systems may list directories in different order, and with this
change we ensure that client code eager loads consistently across platforms,
for example.
Before this release, subdirectories of root directories always represented
namespaces (unless ignored or collapsed). From now on, to be considered
namespaces they also have to contain at least one non-ignored Ruby file with
extension .rb, directly or recursively.
If you know beforehand a certain directory or directory pattern does not
represent a namespace, it is intentional and more efficient to tell Zeitwerk
to ignore it.
However, if you don't do so and have a directory tasks that only contains
Rake files, arguably that directory is not meant to represent a Ruby module.
Before, Zeitwerk would define a top-level Tasks module after it; now, it
does not.
This feature is also handy for projects that have directories with auxiliary
resources mixed in the project tree in a way that is too dynamic for an ignore
pattern to be practical. See #216.
In the unlikely case that an existing project has an empty directory for the
sole purpose of defining a totally empty module (no code, and no nested
classes or modules), such module has now to be defined in a file.
Directories are scanned again on reloads.
On setup, loaders created with Zeitwerk::Loader.for_gem issue warnings if
lib has extra, non-ignored Ruby files or directories.
This is motivated by existing gems with directories under lib that are not
meant to define Ruby modules, like directories for Rails generators, for
instance.
This warning can be silenced in the unlikely case that the extra stuff is
actually autoloadable and has to be managed by Zeitwerk.
Please, check the documentation for
further details.
This method returns an instance of a private subclass of Zeitwerk::Loader
now, but you cannot rely on the type, just on the interface.
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 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)
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
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?
↗️ globalid (indirect, 1.0.0 → 1.0.1) · Repo · Changelog
Security Advisories 🚨
🚨 ReDoS based DoS vulnerability in GlobalID
Release Notes
1.0.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
Bump version for releaseFix ReDoS vulnerability in name parsing↗️ concurrent-ruby (indirect, 1.1.9 → 1.2.2) · Repo · Changelog
Release Notes
1.2.2
1.2.1
1.2.0
1.1.10
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.
↗️ i18n (indirect, 1.10.0 → 1.12.0) · Repo · Changelog
Release Notes
1.12.0
1.11.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
Bump to 1.12.0Merge pull request #633 from ruby-i18n/revert-630-movermeyer/pluralization_cldr_supportRevert "Add support for CLDR data in `I18n::Backend::Pluralization`"Bump to 1.11.0Merge pull request #630 from movermeyer/movermeyer/pluralization_cldr_supportMerge pull request #631 from movermeyer/movermeyer/typosMerge pull request #628 from sambostock/bulk-translation-missing[TYPO] `optoins` -> `options`[TYPO] `explictly` -> `explicitly`[TYPO] `occurences` -> `occurrences`[TYPO] `transfering` -> `transferring`[TYPO] `Reolve` -> `Resolve`[TYPO] `existant` -> `existent`[TYPO] `succesfully` -> `successfully`[TYPO] `supress` -> `suppress`[TYPO] `translitarate` -> `transliterate`[TYPO] `explicitely` -> `explicitly`Add support for CLDR rules in `I18n::Backend::Pluralization`Consistently return array on bulk lookupAdd test for existing bulk lookup failure behavior↗️ tzinfo (indirect, 2.0.4 → 2.0.6) · Repo · Changelog
Release Notes
2.0.6
2.0.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 39 commits:
Fix formatting.Preparing v2.0.6.Add v1.2.11 from the 1.2 branch.Update copyright years.Eliminate Object#untaint deprecation warnings on JRuby 9.4.0.0.Add Ruby 3.2 and JRuby 9.4.Update the dependency on actions/checkout.Fix include issues with tests on Ruby 3.2.Revert "Workaround for 'Permission denied - NUL' errors with JRuby on Windows."Preparing v2.0.5.Add v0.3.61 and v1.2.10 from the 0.3 and 1.2 branches.Fix relative path loading tests.Add a top level eager_load! method for Rails compatibility.Support preloading all data from a DataSource.Clarify that both files and directories are excluded.Tidy up of security file ignoring.Merge pull request #133.Workaround for 'Permission denied - NUL' errors with JRuby on Windows.ignore SECURITY file for Arch tzdata packageAdd Ruby 3.1.Update copyright years.Update copyright years.Fix documentation.Fix a typo.Continue to use philr/setup-ruby@legacy for Ruby 2.0.0 x86 on Windows.Add JRuby 9.3 and update to TruffleRuby 21.Switch to ruby/setup-ruby for 1.9.3 (non-Windows) and 2.0.0.Always return DateTime results using the proleptic Gregorian calendar.Tidy up syntax.Fix a grammatical error.Add version 0.3.60 from the 0.3 branch.Remove an unnecessary or.Add RubyGems logo.Ignore more warnings from sub-processes.Mark truffleruby as experimental.Limit json to < 2.5.0 on Windows Ruby 2.0.Switch to GitHub Actions for CI.[ci skip] Add version 0.3.59 from the 0.3 branch.[ci skip] Improve formatting.↗️ zeitwerk (indirect, 2.5.4 → 2.6.7) · Repo · Changelog
Release Notes
2.6.7 (from changelog)
2.6.6 (from changelog)
2.6.5 (from changelog)
2.6.4 (from changelog)
2.6.3 (from changelog)
2.6.2 (from changelog)
2.6.1 (from changelog)
2.6.0 (from changelog)
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 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