An in-range update of sinon is breaking the build 🚨
greenkeeper opened this issue · comments
Version 5.0.9 of sinon was just published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency |
sinon
|
| Current Version | 5.0.8 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Commits
The new version differs by 5 commits.
86b930cUpdate docs/changelog.md and set new release id in docs/_config.yml033aa60Add release documentation for v5.0.933210855.0.99f321d5Update History.md and AUTHORS for new releasee862196Upgrade@std/esmtoesm.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
After pinning to 5.0.8 your tests are passing again. Downgrade this dependency 📌.
Version 5.0.10 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Commits
The new version differs by 9 commits.
4313d2dUpdate docs/changelog.md and set new release id in docs/_config.ymle21c92aAdd release documentation for v5.0.1041d0dcb5.0.10928379cUpdate History.md and AUTHORS for new release5ca48d3Merge pull request #1802 from ifrost/feature/restore-default-sandbox-fake-timers087bc1cCache reverse functiond19a4c0Add issue number6799e1cUse fakeTimers in the default sandbox8b6f8a8Revert spied fakeTimers to original state
See the full diff
I don't know if anything was explicitly wrong with 5.0.9; the test failures seemed to come from not being able to find 5.0.9 on npm. Anyhow, the tests pass and the version range is open, so closing.