search

alpersonalwebsite / node-express-mongo-db

Node, Express and MongoDB
MIT License
0 stars 1 forks source link

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

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 4 years ago

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency nodemon was updated from 2.0.3 to 2.0.4.

🚨 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 - ❌ **WhiteSource Security Check:** The Security Check found 1 vulnerabilities.
| Severity | CVSS Score |CVE | GitHub Issue | | ------------- |-------------|-----|------| | High | 8.1 | [WS-2020-0070](https://hackerone.com/reports/712065 "Go to CVE Details") | [#18](https://github.com/alpersonalwebsite/node-express-mongo-db/issues/18 "Go to GitHub Issue")
Scan token: 69668cdeef2242b986ce8eec42a787f5 - ✅ **Travis CI - Branch:** The build **passed**.
Release Notes for v2.0.4

2.0.4 (2020-05-14)

Bug Fixes

Commits

The new version differs by 3 commits.

  • a74f5dc fix: add funding in package
  • 43def51 docs: Fix run-on sentence (#1704)
  • f18286e docs: update issue templates

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] commented 4 years ago

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