An in-range update of fetch-mock 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 fetch-mock was updated from 9.3.0 to 9.3.1.

🚨 View failing branch.

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

fetch-mock 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

• ❌ test (12): There are 2 failures, 0 warnings, and 0 notices.
• ❌ test (10): There are 2 failures, 0 warnings, and 0 notices.
• ❌ test (8): There are 1 failures, 0 warnings, and 0 notices.

---

Commits

The new version differs by 7 commits.

• d22e983 linked to cheatsheet EVERYWHERE
• 1d2557d Merge pull request #524 from wheresrhys/cheatsheet
• 1dfc6c2 completed cheatsheet
• 7efa6c5 cheatsheet formatting
• 438c835 refined set up/teardown section of cheatsheet
• 6a2d449 midway through writing cheatsheet content
• 633cf3e improve documentation for when to use a named matcher

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 9.3.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[github-actions]

🎉 This issue has been resolved in version 2.4.4 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀