search

Kronos-JMF / jmf

Base model of the Java script Modelling Framework
0 stars 0 forks source link

An in-range update of assert is breaking the build 🚨 #93

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency assert was updated from 1.4.1 to 1.5.0.

🚨 View failing branch.

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

assert 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 could not complete due to an error ([Details](https://travis-ci.org/Kronos-JMF/jmf/builds/529771755?utm_source=github_status&utm_medium=notification)).
Release Notes for v1.5.0
Commits

The new version differs by 7 commits.

  • 8386769 1.5.0
  • bb3fe66 Update repository URLs.
  • b3c0bcc Fix test name inconsistencies and typos
  • 986fc8d Safely update npm on Travis (#42)
  • 8002bc1 Expose strict mode functionality (#41)
  • 3d981b5 [doc] Explain relation to node.js and the CJS UT spec. (#28)
  • f8975ca Add deepStrictEqual to the README (#23)

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 5 years ago

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