-
Notifications
You must be signed in to change notification settings - Fork 8
Update noflo to the latest version 🚀 #14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: gh-pages
Are you sure you want to change the base?
Conversation
Version 1.0.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 42 commits.
There are 42 commits in total. See the full diff |
Version 1.0.2 just got published. |
Version 1.0.3 just got published.Update to this version instead 🚀 Release Notes1.0.3Added support for running arbitrary NoFlo graphs via CommitsThe new version differs by 6 commits.
See the full diff |
Version 1.1.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 51 commits.
There are 51 commits in total. See the full diff |
Version 1.1.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Version 1.1.3 just got published. |
Version 1.0.0 of noflo was just published.
The version 1.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of noflo.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
1.0.0noflo.AsyncComponentclass -- use WirePattern or Process API insteadnoflo.ArrayPortclass -- use InPort/OutPort withaddressable: trueinsteadnoflo.Portclass -- use InPort/OutPort insteadnoflo.helpers.MapComponentfunction -- use WirePattern or Process API insteadnoflo.helpers.WirePatternlegacy mode -- now WirePattern always uses Process API internallynoflo.helpers.WirePatternsynchronous mode -- useasync: trueand callbacknoflo.helpers.MultiErrorfunction -- send errors via callback or error portnoflo.InPortprocess callback -- use Process APInoflo.InPorthandle callback -- use Process APInoflo.InPortreceive method -- use Process API getX methodsnoflo.InPortcontains method -- use Process API hasX methodsEXPORTSmechanism -- disambiguate with INPORT/OUTPORTscoped: falseon an outport will force all packets sent to that port to be unscopedCommits
The new version differs by 81 commits.
0a65a60Release 1.06af9928Merge pull request #574 from noflo/improve_legacy_detection0774c47Merge pull request #573 from noflo/greenkeeper/fbp-graph-0.3.00a4db51Add tests for legacy API detectionac5c435Don't shadow Splitfbe9db9Move inside the test4333d17fix(package): update fbp-graph to version 0.3.060a6bb6Mention legacy warningff6e014Merge pull request #572 from noflo/warn_legacybd3d5fdTreat old WirePattern as legacyb37ab85Subgraphs are not legacy4259bb2Simplify with isBrowser0cbe985Warn about components using legacy APIs180b462Link to the 1.0 prep blog post195fc5fMerge pull request #571 from noflo/greenkeeper/fbp-graph-0.2.0There are 81 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴