Closed greenkeeper[bot] closed 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.
Your tests are still failing with this version. Compare the changes 🚨
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
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 10 commits.
bd0bf7c
Bump
9cde560
chore(package): update noflo-component-loader to version 0.1.2
49cbe83
Bump
f6ac38e
Merge pull request #30 from noflo/noflo_component_loader
9935b00
Try to match also Windows paths with regexp
c188098
Bump noflo-component-loader dep
84cec54
Update to legacy-free component versions
821de79
Test on modern Node.js
ea16584
Use noflo-component-loader to build the loader
f00089b
Remove obsolete grunt-noflo-manifest
See the full diff
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 6 commits.
4c6bbc6
Bump
36829a2
Merge pull request #31 from noflo/noflo-1.0.0
a0e76e1
Babelize CoffeeScript, NoFlo and fbp-graph for PhantomJS compat
f8a91ab
Merge remote-tracking branch 'origin/greenkeeper/coffee-loader-0.9.0' into noflo-1.0.0
f4144e4
Make fixture depend on NoFlo 1.0
a89a242
fix(package): update coffee-loader to version 0.9.0
See the full diff
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 5 commits.
2f5efa3
Bump
a4e82a4
Bump noflo-component-loader dep
3181641
Test with newer noflo-runtime-postmessage
ad44a8a
Merge pull request #32 from noflo/greenkeeper/noflo-component-loader-0.2.0
ab99dee
fix(package): update noflo-component-loader to version 0.2.0
See the full diff
Version 1.3.0 of grunt-noflo-browser just got published.
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-facebook/builds/263451568?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: