An in-range update of sinon is breaking the build π¨
greenkeeper opened this issue Β· 1 comments
Version 4.0.1 of sinon just got published.
Branch | Build failing π¨ |
---|---|
Dependency | sinon |
Current Version | 4.0.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As sinon 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 πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 16 commits.
ec9126c
Update docs/changelog.md and set new release id in docs/_config.yml
1222a0f
Add release documentation for v4.0.1
1bf1f2d
4.0.1
1545c26
Update History.md and AUTHORS for new release
e9fab2d
Merge pull request #1579 from fatso83/upgrade-deps
f2252b4
Upgrade nise and lolex versions
d81a937
Fix doc typo: scenarious -> scenarios
af3a645
Merge pull request #1577 from evan-007/fix_doc_typo
7c9c881
Remove extra backtick from fake-xhr-and-server docs
cf9bf05
Merge pull request #1575 from mroderick/tidy-up-docs
2e8abad
Remove obsoleted lib/sinon/sandbox-stub.js
28e70d1
Use an include for migration guides
3c68adc
Move migration guides to new section
6197ff3
Merge pull request #1565 from fatso83/patch-docs
dfb9ee6
Add migration guide for 4.0
There are 16 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
After pinning to 4.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.