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.

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

Update selenium-webdriver: 3.14.1 → 3.142.7 (minor) #224

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

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Dec 29, 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.14.1 → 3.142.7) · Repo

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

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

Release Notes

3.0.0

  • #156: Remove unused rubyforge_project from gemspec
  • #160: Remove extension to conditionally install ffi gem on Windows platforms
  • #160: Remove runtime dependency on rake gem

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 41 commits:

↗️ ffi (indirect, 1.9.25 → 1.11.3) · Repo · Changelog

Release Notes

1.11.3 (from changelog)

Removed:

  • Remove support for tainted objects which cause deprecation warnings in ruby-2.7. #730

1.11.2 (from changelog)

Added:

  • Add DragonFlyBSD as a platform. #724

Changed:

  • Sort all types.conf files, so that files and changes are easier to compare.
  • Regenerated type conf for freebsd12 and x86_64-linux targets. #722
  • Remove MACOSX_DEPLOYMENT_TARGET that was targeting very old version 10.4. #647
  • Fix library name mangling for non glibc Linux/UNIX. #727
  • Fix compiler warnings raised by ruby-2.7
  • Update libffi to latest master.

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

1.10.0 (from changelog)

Added:

  • Add /opt/local/lib/ to ffi's fallback library search path. #638
  • Add binary gem support for ruby-2.6 on Windows
  • Add FreeBSD on AArch64 and ARM support. #644
  • Add FFI::LastError.winapi_error on Windows native or Cygwin. #633

Changed:

  • Update to rake-compiler-dock-0.7.0
  • Use 64-bit inodes on FreeBSD >= 12. #644
  • Switch time_t and suseconds_t types to long on FreeBSD. #627
  • Make register_t long_long on 64-bit FreeBSD. #644
  • Fix Pointer#write_array_of_type #637

Removed:

  • Drop binary gem support for ruby-2.0 and 2.1 on Windows

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 → 2.0.0) · Repo · Changelog

Release Notes

2.0.0

Security

  • 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
  • Drop support for unsupported ruby versions #406

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 52 commits:


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

@depfu depfu bot added the depfu label Dec 29, 2019
@depfu depfu bot force-pushed the depfu/update/selenium-webdriver-3.142.7 branch 3 times, most recently from 1acd2cf to 1fd2d92 Compare December 29, 2019 14:58
@depfu depfu bot force-pushed the depfu/update/selenium-webdriver-3.142.7 branch from 1fd2d92 to 7d3df52 Compare December 29, 2019 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants