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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update flow-bin to the latest version 馃殌 #661

merged 2 commits into from Apr 28, 2017


None yet
1 participant
Copy link

greenkeeper bot commented Apr 28, 2017

Version 0.45.0 of flow-bin just got published.

Dependency flow-bin
Current Version 0.44.2
Type devDependency

The version 0.45.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of flow-bin.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


The new version differs by 1 commits0.


See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 馃尨

@greenkeeper greenkeeper bot added the greenkeeper label Apr 28, 2017

@helfer helfer merged commit 6b50a23 into master Apr 28, 2017

5 checks passed

./dist/index.min.js.gz No change (17,748 bytes)
CLA Author has signed the Meteor CLA.
continuous-integration/travis-ci/pr The Travis CI build passed
continuous-integration/travis-ci/push The Travis CI build passed
coverage/coveralls Coverage remained the same at 92.308%

@helfer helfer deleted the greenkeeper/flow-bin-0.45.0 branch Apr 28, 2017

@jbaxleyiii jbaxleyiii referenced this pull request May 1, 2017


Release 1.1.3 #676

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment