unexpected just published its new version 10.26.3.
State
Failing tests :warning:
Dependency
unexpected
New version
10.26.3
Type
devDependency
This version is covered by your current version range and after updating it in your project the build kept failing.
It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.
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.3.
This version is covered by your current version range and after updating it in your project the build kept failing.
It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.
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 213 commits .
ec9bebf
10.26.3
61af9d2
Build unexpected.js
fe873d0
Merge pull request #381 from unexpectedjs/fix/toExhaustivelySatisfyWithMissingKey
4ee3d58
Fix the error message when an object is exhaustively satisfied against an object, and some keys are missing
5fb884a
Merge pull request #379 from unexpectedjs/sunesimonsen/upgrade-jest
3bf09cf
Upgraded Jest to the newest version
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
There are 213 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.