🚨 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 upgrade. Please take a good look at what changed and the test results before merging this pull request.
The help command now displays a help message directly, instead of opening a ri console.
You can now get detailed usage information for specific commands by using help <cmd>. Commands that currently support detailed help messages include:
show_source
show_doc
edit
ls
We welcome contributions to expand this list!
The show_source command can now display methods defined during the IRB session.
In irb:rdbg sessions, simply hitting <enter> will now repeat the last command, mirroring the behavior in rdbg sessions.
IRB now supports loading .irbrc from multiple locations. This means that for most users, ~/.irbrc will also be loaded when a project/.irbrc is defined.
Third time’s a charm? Remember: ‘ensure’ is almost always the wrong way to go (for results… it’s great for cleaning up).
5.22.1 (from changelog)
1 bug fix:
Don’t exit non-zero if no tests ran and no filter (aka, the test file is empty). (I’m starting to think the exit 1 thing for @tenderlove was a mistake…)
5.22.0 (from changelog)
1 minor enhancement:
Added “did you mean” output if your –name filter matches nothing. (tenderlove)
2 bug fixes:
Big cleanup of test filtering. Much prettier / more functional.
Fix situation where Assertion#location can’t find the location. (pftg)
[CRuby] XML::Reader sets the @encoding instance variable during reading if it is not passed into the initializer. Previously, it would remain nil. The behavior of Reader#encoding has not changed. This works around changes to how libxml2 reports the encoding used in v2.12.6.
There is a possible denial of service vulnerability in the header parsing
routines in Rack. This vulnerability has been assigned the CVE identifier
CVE-2024-26146.
Versions Affected: All. Not affected: None Fixed Versions: 2.0.9.4, 2.1.4.4, 2.2.8.1, 3.0.9.1
Impact
Carefully crafted headers can cause header parsing in Rack to take longer than
expected resulting in a possible denial of service issue. Accept and Forwarded headers are impacted.
Ruby 3.2 has mitigations for this problem, so Rack applications using
Ruby 3.2 or newer are unaffected.
Releases
The fixed releases are available at the normal locations.
There is a possible DoS vulnerability relating to the Range request header in
Rack. This vulnerability has been assigned the CVE identifier CVE-2024-26141.
Carefully crafted Range headers can cause a server to respond with an
unexpectedly large response. Responding with such large responses could lead
to a denial of service issue.
Vulnerable applications will use the Rack::File middleware or the Rack::Utils.byte_ranges methods (this includes Rails applications).
Releases
The fixed releases are available at the normal locations.
There is a possible denial of service vulnerability in the content type
parsing component of Rack. This vulnerability has been assigned the CVE
identifier CVE-2024-25126.
Carefully crafted content type headers can cause Rack’s media type parser to
take much longer than expected, leading to a possible denial of service
vulnerability.
Impacted code will use Rack’s media type parser to parse content type headers.
This code will look like below:
request.media_type
## OR
request.media_type_params
## OR
Rack::MediaType.type(content_type)
Some frameworks (including Rails) call this code internally, so upgrading is
recommended!
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.
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)
🚨 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 upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rspec-rails (6.1.1 → 6.1.2) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
↗️ bigdecimal (indirect, 3.1.5 → 3.1.7) · Repo · Changelog
Release Notes
3.1.7
3.1.6
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.
↗️ diff-lcs (indirect, 1.5.0 → 1.5.1) · Repo · Changelog
Release Notes
1.5.1 (from changelog)
Does any of this look wrong? Please let us know.
↗️ drb (indirect, 2.2.0 → 2.2.1) · Repo
Release Notes
2.2.1
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.14.1 → 1.14.4) · Repo · Changelog
Release Notes
1.14.4
1.14.3
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.
↗️ io-console (indirect, 0.7.1 → 0.7.2) · Repo
Release Notes
0.7.2
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.
↗️ irb (indirect, 1.11.1 → 1.12.0) · Repo
Release Notes
1.12.0
1.11.2
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.
↗️ minitest (indirect, 5.21.2 → 5.22.3) · Repo · Changelog
Release Notes
5.22.2 (from changelog)
5.22.1 (from changelog)
5.22.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.
↗️ nokogiri (indirect, 1.16.2 → 1.16.3) · Repo · Changelog
Release Notes
1.16.3
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.8 → 2.2.8.1) · Repo · Changelog
Security Advisories 🚨
🚨 Possible Denial of Service Vulnerability in Rack Header Parsing
🚨 Possible DoS Vulnerability with Range Header in Rack
🚨 Denial of Service Vulnerability in Rack Content-Type Parsing
Release Notes
2.2.8.1
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.
↗️ reline (indirect, 0.4.2 → 0.4.3) · Repo
Release Notes
0.4.3
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.
↗️ rspec-core (indirect, 3.12.2 → 3.13.0) · Repo · Changelog
Release Notes
3.13.0 (from changelog)
3.12.3 (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.
↗️ rspec-expectations (indirect, 3.12.3 → 3.13.0) · Repo · Changelog
Release Notes
3.13.0 (from changelog)
3.12.4 (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.
↗️ rspec-mocks (indirect, 3.12.6 → 3.13.0) · Repo · Changelog
Release Notes
3.13.0 (from changelog)
3.12.7 (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.
↗️ rspec-support (indirect, 3.12.1 → 3.13.1) · Repo · Changelog
Release Notes
3.13.1 (from changelog)
3.13.0 (from changelog)
3.12.2 (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.
↗️ thor (indirect, 1.3.0 → 1.3.1) · Repo · Changelog
Release Notes
1.3.1
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.
↗️ zeitwerk (indirect, 2.6.12 → 2.6.13) · Repo · Changelog
Release Notes
2.6.13 (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.
🗑️ ruby2_keywords (removed)
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