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

[greenkeeper[bot]]

The devDependency nodemon was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

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

nodemon 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/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/nhsuk/connecting-to-services/builds/623704788?utm_source=github_status&utm_medium=notification)).

---

Release Notes for v2.0.2

2.0.2 (2019-12-11)

Bug Fixes

• pipe stderr correctly (47dfb8b), closes #1638

Commits

The new version differs by 3 commits.

• cd45d74 test: fix fork test
• 496c335 chore: undo change to spawn code
• 47dfb8b fix: pipe stderr correctly

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 2.0.1 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper[bot]]

• The devDependency nodemon was updated from 2.0.2 to 2.0.3.

Your tests are still failing with this version. Compare changes

Release Notes for v2.0.3

2.0.3 (2020-04-08)

Bug Fixes

• package.json & package-lock.json to reduce vulnerabilities (a4490e2)

Commits

The new version differs by 5 commits.

• ee92ee4 test: split require tests
• 33ae6da test: fix failing test when required
• a4490e2 fix: package.json & package-lock.json to reduce vulnerabilities
• 9bd07eb docs: changed verbose logging and CLI documentation to reflect support single file watch functionality
• c279760 test: make sigint test to actually check child pid (#1656)

See the full diff