The version 10.30.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 unexpected.
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.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 10.30.0 of unexpected just got published.
The version 10.30.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 unexpected. 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.
Commits
The new version differs by 13 commits.
85b05a7
10.30.0
bc4c2ad
Build unexpected.js
ead3f86
Merge pull request #387 from unexpectedjs/feature/inspectArrowFunctions
4aa8aa3
Merge pull request #396 from unexpectedjs/feature/improveCompoundAssertionError
c0e09a3
Merge pull request #400 from unexpectedjs/fix/chainingOfInstallThemeAndAddStyle
ff3eb39
addStyle & installTheme: Return the expect function rather than the magicpen instance (for chaining)
0873448
Travis: Build with node.js 8
321fb8e
Copy the new example to the 'to throw' documentation, too.
0daf53f
Merge pull request #398 from nover/master
0bf76b9
Document will-throw-a assertions for functions that take input
ae3c0c6
Avoid using the 'in' operator (could be fooled by eg. 'toString')
a2d7e79
Don't allow a compound assertion where the last half is not (the prefix of) an existing assertion.
4485bf6
Support inspection of arrow functions
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: