noflo / noflo-runtime

FBP runtime components for NoFlo
MIT License
11 stars 10 forks source link

An in-range update of noflo-core is breaking the build 🚨 #157

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency noflo-core was updated from 0.5.0 to 0.6.0.

🚨 View failing branch.

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

noflo-core 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/noflo/noflo-runtime/builds/465168146?utm_source=github_status&utm_medium=notification)).

Commits

The new version differs by 41 commits.

  • 2a0a23f Release 0.6.0
  • 47ad50c Merge pull request #128 from noflo/update_eslint
  • 1662300 Adapt eslint rules for mocha tests
  • e64d60e Update eslint
  • 8fb84c9 chore(package): update eslint to version 5.0.1
  • 7443f82 chore(package): update eslint-config-airbnb-base to version 13.0.0
  • db433d9 Merge pull request #124 from noflo/greenkeeper/nyc-12.0.1
  • cff01d5 chore(package): update nyc to version 12.0.1
  • 1494dcb Add changelog
  • c1250f8 Merge pull request #125 from noflo/decaf
  • ec50169 Clean up the specs
  • ba63c6a Run without browser tests for the while
  • 56e2442 Fix Chrome headless on Travis
  • 2857496 Use Chrome from Puppeteer
  • 8f08f13 Try testing with karma

There are 41 commits in total.

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

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 11 commits.

  • 80579bb Prepare 0.6.1
  • 7917317 Make interval deactivate when stopped
  • 0376907 Merge pull request #129 from noflo/browser_testing
  • 1404327 Bump noflo-webpack-config dep
  • 46a1f22 noflo, chai, baseDir are global now
  • cd02511 Get inject file from noflo-webpack-config
  • b4a03a1 Run Mocha tests also in browser
  • 81fed11 Run fbp-specs on both Node and browser
  • c867c5b Move mocha tests to their own folder
  • e3fc9f5 Use noflo-webpack-config presets for browser build
  • a68e83e Remove Grunt

See the full diff