This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
Update noflo-strings to the latest version 🚀 #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 0.4.0 of noflo-strings was just published.
The version 0.4.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-strings.
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.
Commits
The new version differs by 14 commits.
301a474Bumpc142775Merge pull request #102 from noflo/greenkeeper/noflo-1.0.03d91de5Use CoffeeScript 270b6d97Build with newer grunt-noflo-browserd1fb1cdRemove obsolete manifest info314db0cDepend with a hatda01886Merge remote-tracking branch 'origin/greenkeeper/grunt-contrib-coffee-2.0.0' into greenkeeper/noflo-1.0.01a7f3f3fix(package): update noflo to version 1.0.00d90ab0chore(package): update grunt-contrib-coffee to version 2.0.0c6b9d5aMerge pull request #100 from noflo/greenkeeper/grunt-noflo-browser-1.4.0a3bd39cTest on newer Node.js9605457chore(package): update grunt-noflo-browser to version 1.4.0b442ddaMerge pull request #98 from noflo/greenkeeper/mocha-4.0.0cbc638fchore(package): update mocha to version 4.0.0See 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 🌴