The version 0.6.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 osprey-router.
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.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 97.72% when pulling 695e89242f79f7414dc06d2dc1cd29aa19fcbe1d on greenkeeper/osprey-router-0.6.0 into 2dda6ba4d759d2d14e9796af9d492986c87a7fec on master.
Coverage remained the same at 97.72% when pulling 695e89242f79f7414dc06d2dc1cd29aa19fcbe1d on greenkeeper/osprey-router-0.6.0 into 2dda6ba4d759d2d14e9796af9d492986c87a7fec on master.
Coverage remained the same at 97.72% when pulling 695e89242f79f7414dc06d2dc1cd29aa19fcbe1d on greenkeeper/osprey-router-0.6.0 into 2dda6ba4d759d2d14e9796af9d492986c87a7fec on master.
Coverage remained the same at 97.72% when pulling 695e89242f79f7414dc06d2dc1cd29aa19fcbe1d on greenkeeper/osprey-router-0.6.0 into 2dda6ba4d759d2d14e9796af9d492986c87a7fec on master.
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 0.6.0 of osprey-router was just published.
The version 0.6.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 osprey-router.
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 7 commits.
c800c94
0.6.0
a1862ad
updated dependencies
9e37182
Merge pull request #15 from mulesoft-labs/greenkeeper/initial
f3eabd0
updating Travis
3e05619
update for standard 11.0.0
0ce637c
docs(readme): add Greenkeeper badge
2ff7e85
chore(package): update dependencies
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: