An in-range update of snyk is breaking the build 🚨

[greenkeeper[bot]]

---

☝️ 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 snyk was updated from 1.312.0 to 1.313.0.

🚨 View failing branch.

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

snyk 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

- ❌ **Unit Tests:** null

---

Release Notes for v1.313.0

1.313.0 (2020-04-27)

Features

• enable experimental docker-archive scanning (5e627c6)

Commits

The new version differs by 2 commits.

• b59f0b5 Merge pull request #1087 from snyk/feat/experimental-docker-archive
• 5e627c6 feat: enable experimental docker-archive scanning

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 1.312.0 your tests are passing again. Downgrade this dependency 📌.

[thislooksfun]

Failure was due to stale npm caches, not the update itself.