An in-range update of chrome-launcher is breaking the build 🚨

[greenkeeper]

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The devDependency chrome-launcher was updated from 0.13.0 to 0.13.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

chrome-launcher is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

---

Commits

The new version differs by 2 commits.

• d4d8221 v0.13.1
• bf2957a deps: update various dependencies (#192)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 0.13.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The devDependency chrome-launcher was updated from 0.13.1 to 0.13.2.

Your tests are still failing with this version. Compare changes

Release Notes for 0.13.2 (Thu, May 7 2020)

• 7c1ea547 deps: bump to is-wsl@2.2.0 (#187)
• 2ae5591d fix: sanitize environment variables used in RegExp (#197)

Commits

The new version differs by 5 commits.

• d703582 v0.13.2
• 7c1ea54 deps: bump to is-wsl@2.2.0 (#187)
• 2ae5591 fix: sanitize environment variables used in RegExp (#197)
• 9aa64d6 add prepublish script (#193)
• 2289dcd update changelog

See the full diff