Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update selenium-webdriver: 3.141.0 → 3.142.5 (minor) #71

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update selenium-webdriver: 3.141.0 → 3.142.5 (minor) #71

wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Oct 2, 2019

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.141.0 → 3.142.5) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ childprocess (indirect, 0.9.0 → 2.0.0) · Repo · Changelog

Release Notes

2.0.0 (from changelog)

  • #148: Drop support for Ruby 2.0, 2.1, and 2.2
  • #149: Fix Unix fork reopen to be compatible with Ruby 2.6
  • #152/#154: Fix hangs and permission errors introduced in Ruby 2.6 for leader processes of process groups

1.0.1 (from changelog)

  • #143: Fix installs by adding rake gem as runtime dependency
  • #147: Relax rake gem constraint from < 12 to < 13

1.0.0 (from changelog)

  • #134: Add support for non-ASCII characters on Windows
  • #132: Install ffi gem requirement on Windows only
  • #128: Convert environment variable values to strings when posix_spawn enabled
  • #141: Support JRuby on Java >= 9

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

Commits

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

↗️ ffi (indirect, 1.10.0 → 1.11.1) · Repo · Changelog

Release Notes

1.11.1 (from changelog)

Changed:

  • Raise required ruby version to >=2.0. #699, #700
  • Fix a possible linker error on ruby < 2.3 on Linux.

1.11.0 (from changelog)

Added:

  • Add ability to disable or force use of system libffi. #669 Use like gem inst ffi -- --enable-system-libffi .
  • Add ability to call FFI callbacks from outside of FFI call frame. #584
  • Add proper documentation to FFI::Generator and ::Task
  • Add gemspec metadata. #696, #698

Changed:

  • Fix stdcall on Win32. #649, #669
  • Fix load paths for FFI::Generator::Task
  • Fix FFI::Pointer#read_string(0) to return a binary String. #692
  • Fix benchmark suite so that it runs on ruby-2.x
  • Move FFI::Platform::CPU from C to Ruby. #663
  • Move FFI::StructByReference to Ruby. #681
  • Move FFI::DataConverter to Ruby (#661)
  • Various cleanups and improvements of specs and benchmarks

Removed:

  • Remove ruby-1.8 and 1.9 compatibility code. #683
  • Remove unused spec files. #684

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.

↗️ rubyzip (indirect, 1.2.2 → 1.3.0) · Repo · Changelog

Release Notes

1.3.0

Security

  • 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

Tooling / Documentation

  • Add more gem metadata links #402

1.2.4

  • Do not rewrite zip files opened with open_buffer that have not changed #360

Tooling / Documentation

  • Update example_recursive.rb in README #397
  • Hold CI at trusty for now, automatically pick the latest ruby patch version, use rbx-4 and hold jruby at 9.1 #399

1.2.3

  • Allow tilde in zip entry names #391 (fixes regression in 1.2.2 from #376)
  • Support frozen string literals in more files #390
  • Require pathname explicitly #388 (fixes regression in 1.2.2 from #376)

Tooling / Documentation:

  • CI updates #392, #394
    • Bump supported ruby versions and add 2.6
    • JRuby failures are no longer ignored (reverts #375 / part of #371)
  • Add changelog entry that was missing for last release #387
  • Comment cleanup #385

Since the GitHub release information for 1.2.2 is missing, I will also include it here:

1.2.2

NB: This release drops support for extracting symlinks, because there was no clear way to support this securely. See #376 (comment) for details.

  • Fix CVE-2018-1000544 #376 / #371
  • Fix NoMethodError: undefined method `glob' #363
  • Fix handling of stored files (i.e. files not using compression) with general purpose bit 3 set #358
  • Fix close on StringIO-backed zip file #353
  • Add Zip.force_entry_names_encoding option #340
  • Update rubocop, apply auto-fixes, and fix regressions caused by said auto-fixes #332, #355
  • Save temporary files to temporary directory (rather than current directory) #325

Tooling / Documentation:

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

Commits

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

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

  • Circle CI, Semaphore and Travis-CI are all excellent options.
  • If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
  • If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

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

@depfu depfu bot added the depfu label Oct 2, 2019
@depfu depfu bot mentioned this pull request Oct 2, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
depfu
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants