The version 2.1.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 assume.
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 95.413% when pulling 8574201874a6e8b7acf9d38e31db2753df9df503 on greenkeeper/assume-2.1.0 into f25888ffc67d21beaa1572b53ab6704a67266b64 on master.
Coverage remained the same at 95.413% when pulling 8574201874a6e8b7acf9d38e31db2753df9df503 on greenkeeper/assume-2.1.0 into f25888ffc67d21beaa1572b53ab6704a67266b64 on master.
Version 2.1.0 of assume was just published.
assume
The version 2.1.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 assume.
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 22 commits.
b9eac66
[dist] 2.1.0
9fb8335
Merge pull request #25 from msluther/past-tense
6dc97db
[tiny] Add past-tense verbiage
3346333
[travis] Djeez, stop complaining travis, we know you work as intended
df4acd0
[dist] 2.0.1
ddc5794
[test] Fixed test file reference
e6997e4
[fix] Remove all unneeded ES6 references from the code base. #23
ef02aea
[dist] 2.0.0
7e1a6d4
[minor] Added more type detections
f001e95
[minor] Better syntax for thenables
55491be
[minor] Reformat
fc68885
[merge] Manually merge #24 because of merge conflicts
38bda88
Merge pull request #23 from bigpipe/modernize
ef92e11
[minor] Remove mochify
27cb2e1
[deps] Bump dependencies
There are 22 commits in total.
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: