🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
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.
This version 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 simple-mock.
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.
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.
Coverage remained the same at 93.591% when pulling 735ad6d4e802a7278c272164feafa5a3d9654e70 on greenkeeper-simple-mock-0.8.0 into 7207cdab5697b682787e3d05c3307b7ff3eb2a0e on master.
Coverage remained the same at 93.591% when pulling 735ad6d4e802a7278c272164feafa5a3d9654e70 on greenkeeper-simple-mock-0.8.0 into 7207cdab5697b682787e3d05c3307b7ff3eb2a0e on master.
Coverage remained the same at 93.591% when pulling 735ad6d4e802a7278c272164feafa5a3d9654e70 on greenkeeper-simple-mock-0.8.0 into 7207cdab5697b682787e3d05c3307b7ff3eb2a0e on master.
Hello lovely humans,
simple-mock just published its new version 0.8.0.
This version 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 simple-mock. 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.
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 6 commits .
10a2dc1
0.8.0
1d41cad
Merge pull request #24 from HCanber/rejectWith
799621d
Create resolved promises when the mock is called and not when configured
af99748
Create rejected promises when the mock is called and not when configured
8bf9923
Add test that shows that rejectWith promises generates warnings
e2e48ec
Restore mocked simple.Promise after test runs
See the full diff.