unexpected just published its new version 10.26.2.
State
Failing tests :rotating_light:
Dependency
unexpected
New version
10.26.2
Type
devDependency
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As unexpected is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
unexpected just published its new version 10.26.2.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As unexpected is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 179 commits .
c946158
10.26.2
70ab40f
Build unexpected.js
c94b00d
to satisfy: Don't break when the assertion fails and the subject has a property that also exists on Object.prototype
d60fecf
10.26.1
f14dd8b
Build unexpected.js
4cd6c4c
Merge pull request #376 from Munter/feature/betterAddAssertionFeedback
4eb5b11
Makefile, test target: Don't pass --harmony-async-await now that node 7.6.0 supports async/await without it.
543b474
type.inspect: Fix detection of whether inspect is invoked by util.inspect
a1eaa87
Add assertion type signature to error messages relevant to it
734ca44
10.26.0
77ba2ef
Build unexpected.js
2fef98f
Merge pull request #372 from unexpectedjs/feature/errorWhenHandlerTakesTooManyParameters
8b3b3fd
Fix typo in test description.
8be08a6
Merge pull request #371 from unexpectedjs/fix/toExhaustivelySatisfyDefinedness
0dfe942
addAssertion: Throw an error when the handler takes too many parameters.
There are 179 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.