search

noflo / visualize

Simple FBP visualizer
http://noflojs.org/visualize/
15 stars 8 forks source link

An in-range update of fbp is breaking the build 🚨 #15

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 1.7.0 of fbp was just published.

Branch Build failing 🚨
Dependency fbp
Current Version 1.6.0
Type dependency

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

fbp is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/noflo/visualize/builds/303506384?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 23 commits.

  • 4a87a60 Release 1.7.0
  • eac460d Merge pull request #88 from flowbased/annotations
  • dbb4660 Move newline matching to a named rule
  • 9f15f3d Include node names in data validation errors
  • 0ce2fcd Clean up tests and ensure node names are there
  • 65214c1 Fix FBP serialization in case sensitive mode
  • bd28c52 Document annotations
  • c629173 Add test to verify that multiple arrayport connections on same line are fine, fixes #19
  • 2219408 Allow whitespace in annotation values
  • 8d80841 Move prop check to separate test case
  • 86e3d3b Check properties with roundtrip
  • 55120c7 Add parsing and serialization for annotations
  • 0944d2d We now provide default values
  • 265476d Name is inside props
  • 43e5797 Export textual properties as annotations

There are 23 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 6 years ago

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