Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of sinon is breaking the build 🚨 #87

Open
greenkeeper bot opened this issue Jun 6, 2018 · 1 comment
Open

An in-range update of sinon is breaking the build 🚨 #87

greenkeeper bot opened this issue Jun 6, 2018 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jun 6, 2018

Version 5.1.0 of sinon was just published.

Branch Build failing 🚨
Dependency sinon
Current Version 5.0.10
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 failed Details

Commits

The new version differs by 39 commits.

  • e68ba0d Update docs/changelog.md and set new release id in docs/_config.yml
  • bb0ff41 Add release documentation for v5.1.0
  • 8f867f9 5.1.0
  • 39466a4 Update History.md and AUTHORS for new release
  • 8a4808b finished fixing ie tests
  • 53169e3 Merge pull request #1811 from mhmoudgmal/feature/in-matcher
  • 09f849c Remove notice
  • 01e69a9 cleaning up the fix for #1821
  • fabe894 fixed coveralls integration
  • 5a886bd Fix #1821: fake tests fails on IE 11
  • bed477a Revert PR #1807 to fix #1814
  • 878e2e8 clean up travis config
  • 5e49793 removed node v4; added node v10
  • 81a87d5 Improve tests readability
  • 9d30dcf Merge pull request #1809 from fatso83/esm-module

There are 39 commits in total.

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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jun 6, 2018

After pinning to 5.0.10 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants