Skip to content
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

Update noflo to version 0.6.1 🚀 #36

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello 👋

🚀🚀🚀

noflo just published its new version 0.6.1, which is not covered by your current version range.

If this pull request passes your tests you can publish your software with the latest version of noflo – otherwise use this branch to work on adaptions and fixes.

Happy fixing and merging 🌴


The new version differs by 106 commits .

  • 2203bce Expose IP objects
  • 5cf72a8 Expose IP objects
  • 8dd2d83 CHANGES: noflo executable was removed
  • de2bb3b Update NPM autodeploy
  • f8ef309 Bump
  • 945ca1c Roll out first 0.6.x release, fixes #383
  • 3e1ca1d Merge pull request #406 from trustmaster/master
  • dc59d9d Update Changes
  • 790dc91 Still register the noflo command so users can get the deprecation notice
  • 6e239ce Update copyright strings
  • 333b139 Merge pull request #404 from aretecode/patch-2
  • 4a5a234 Update package.json
  • 7840f13 Update icon via constructor options
  • ddd6cae Bump version
  • 60db9d1 Merge pull request #392 from trustmaster/process_api

There are 106 commits in total. See the full diff.


This pull request was created by greenkeeper.io.
It keeps your software, up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡

@bergie bergie force-pushed the greenkeeper-noflo-0.6.1 branch from 14eb18b to d3de2c8 Compare February 2, 2017 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant