🚨 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.
In Rubyzip before 1.3.0, a crafted ZIP file can bypass application
checks on ZIP entry sizes because data about the uncompressed size
can be spoofed. This allows attackers to cause a denial of service
(disk consumption).
Release Notes
2.3.2 (from changelog)
A "dummy" release to warn about breaking changes coming in version 3.0. This updated version uses the Gem post_install_message instead of printing to STDERR.
Fix (at least partially) the restore_times and restore_permissions options to Zip::File.new#413
Previously, neither option did anything, regardless of what it was set to. We have therefore defaulted them to false to preserve the current behavior, for the time being. If you have explicitly set either to true, it will now have an effect.
Fix handling of UniversalTime (mtime, atime, ctime) fields. #421
Previously, Zip::File did not pass the options to Zip::Entry in some cases. #423
Note that restore_times in this release does nothing on Windows and only restores mtime, not atime or ctime.
Allow Zip::File.open to take an options hash like Zip::File.new#418
Always print warnings with warn, instead of a mix of puts and warn#416
Create temporary files in the system temporary directory instead of the directory of the zip file #411
Default the validate_entry_sizes option to true, so that callers can trust an entry's reported size when using extract#403
This option defaulted to false in 1.3.0 for backward compatibility, but it now defaults to true. If you are using an older version of ruby and can't yet upgrade to 2.x, you can still use 1.3.0 and set the option to true.
Tooling / Documentation
Remove test files from the gem to avoid problems with antivirus detections on the test files #405 / #384
Add validate_entry_sizes option so that callers can trust an entry's reported size when using extract#403
This option defaults to false for backward compatibility in this release, but you are strongly encouraged to set it to true. It will default to true in rubyzip 2.0.
New Feature
Add add_stored method to simplify adding entries without compression #366
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ selenium-webdriver (3.14.0 → 4.11.0) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
↗️ rubyzip (indirect, 1.2.2 → 2.3.2) · Repo · Changelog
Security Advisories 🚨
🚨 Denial of Service in rubyzip ("zip bombs")
Release Notes
2.3.2 (from changelog)
2.3.1
2.3.0
2.2.0
2.1.0
2.0.0
1.3.0
1.2.4
1.2.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.
🆕 rexml (added, 3.2.6)
🆕 websocket (added, 1.2.9)
🗑️ childprocess (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