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 karma is breaking the build 🚨 #98

Closed
greenkeeper bot opened this issue Oct 17, 2019 · 2 comments
Closed

An in-range update of karma is breaking the build 🚨 #98

greenkeeper bot opened this issue Oct 17, 2019 · 2 comments
Labels
bug Something isn't working greenkeeper

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Oct 17, 2019

The devDependency karma was updated from 4.3.0 to 4.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

karma 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
  • ci/circleci: build: Your tests passed on CircleCI! (Details).
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).
  • WhiteSource Security Check: The Security Check found 7 vulnerabilities.

Severity CVSS Score CVE GitHub Issue
High 7.3 WS-2019-0291 #3
Medium 6.1 CVE-2012-6708 #8
Medium 6.1 CVE-2019-11358 #5
Medium 6.1 CVE-2015-9251 #4
Medium 5.0 WS-2019-0043 #2
Medium 4.3 CVE-2011-4969 #7
Medium 4.3 WS-2016-0090 #6

Scan token: a3eb72b00c1d4ef180c4646f4b8ded3e - ✅ **Travis CI - Branch:** The build **passed**.

Release Notes for v4.4.0

Bug Fixes

Features

Commits

The new version differs by 11 commits.

  • fbad778 chore: release v4.4.0
  • 5aa4361 chore: update contributors
  • 4ed3af0 feat(config): add failOnSkippedTests option. (#3374)
  • c7bab36 docs(commit-msg): Add failOnFailingTestSuite option to docs (#3380)
  • 0d70809 feat(deps): Remove core-js dependency. (#3379)
  • 3ffcd83 feat: Preprocessor can return Promise (#3376)
  • f8005c6 fix(runner): remove explicit error on all tests failed (#3369)
  • f2eba15 chore: travis - upgrade on new version Ubuntu 16.04 (#3371)
  • eab7e5b chore(appveyor): Notification config. (#3375)
  • 6235e68 feat(config): clientDisplayNone sets client elements display none. (#3348)
  • 019bfd4 feat(client): Add trusted types support (#3360)

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 🌴

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.96. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the bug Something isn't working label Oct 17, 2019
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Oct 17, 2019

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

@greenkeeper greenkeeper bot closed this as completed Nov 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working greenkeeper
Projects
None yet
Development

No branches or pull requests

0 participants