search

noflo / noflo-finitedomain

Finite Domain Constraint Solving for NoFlo
MIT License
0 stars 2 forks source link

An in-range update of grunt-noflo-browser is breaking the build 🚨 #42

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 1.3.0 of grunt-noflo-browser just got published.

Branch Build failing 🚨
Dependency grunt-noflo-browser
Current Version 1.2.0
Type devDependency

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

As grunt-noflo-browser is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

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

The new version differs by 14 commits.

  • d01f8b1 Update docs, refs #25
  • a7653fd Bump
  • 83d9573 Merge pull request #25 from noflo/opener_protocol
  • 8a8f257 Fix indent
  • cd150ba Provide runtime type correctly
  • 31acbd7 No need to log the debug URL, since we need to go through the button
  • 6321a65 Switch from iframe+webrtc to postmessage runtime
  • b694bb7 README: Minor doc improvements
  • 24f2afa Merge pull request #24 from noflo/greenkeeper/webpack-3.0.0
  • e8c9cce fix(package): update webpack to version 3.0.0
  • 83a6b19 Merge pull request #23 from noflo/greenkeeper/chai-4.0.0
  • d3e2bcf chore(package): update chai to version 4.0.0
  • 361e0ed Update tests for 0.8
  • 1e6ca6e Abort on parse errors

See the full diff

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

After pinning to 1.2.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 7 years ago

Version 1.3.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 7 commits.

  • 33d322c Bump
  • 2510dbf Merge pull request #27 from noflo/getsource
  • c645b5e Include semicolon like in the other template variables
  • 632cbd6 When debug is enabled, store original non-transpiled sources to componentloader
  • 2e86749 Simplify component registration
  • 4a81492 Expect getSource to return original, non-transpiled source code, refs #19
  • d77af32 Keep track of originally provided sources, and return the same for getSource

See the full diff

greenkeeper[bot] commented 7 years ago

Version 1.3.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 4 commits.

  • cf4dbb5 Bump
  • 7b47732 Register library default icons from FBP manifest
  • b3465e1 Merge pull request #29 from noflo/greenkeeper/mocha-4.0.0
  • 2ac3445 chore(package): update mocha to version 4.0.0

See the full diff