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 🚨 #2667

Closed
greenkeeper bot opened this issue Jan 14, 2017 · 1 comment
Closed

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

greenkeeper bot opened this issue Jan 14, 2017 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jan 14, 2017

Version 1.4.0 of karma just got published.

Branch Build failing 🚨
Dependency karma
Current Version 1.3.0
Type devDependency

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

As karma 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/appveyor/branch Waiting for AppVeyor build to complete Details

  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v1.4.0

Bug Fixes

  • browser: filter browser logging by level (35965d9), closes #2228
  • cli: restore shell completion in the npm package (f56b5a5), closes #2351
  • config: add crossOriginAttribute config option (1e465b1)
  • middleware: update Buffer usage (3d94b8c)
  • reporter: do not allow URL domains to span new lines (2c13404)
  • reporter: strip only hostname/port (fbbeccf), closes #2209
  • reporters: cannot read property map of undefined (305df2c), closes #1662
  • server: exit with code 1 when failing due to missing browser (86e2ef2), closes #2403

Features

  • api: add constants to the public api (ee10977), closes #2361
  • api: expose config.parseConfig on the public api (7d2c1ae)
  • client: capture confirm & prompt (3a618b3), closes #694
  • server: add listen address option so that IPv6 and loopback interfaces can be used (8e5bee6), closes #2477
  • web-server: allow overriding of default http module (1e7514d), closes #2424
Commits

The new version differs by 42 commits .

  • 99d647b chore: release v1.4.0
  • c168b79 chore: update contributors
  • fbbeccf fix(reporter): strip only hostname/port
  • 3a618b3 feat(client): capture confirm & prompt
  • 35965d9 fix(browser): filter browser logging by level
  • 305df2c fix(reporters): cannot read property map of undefined
  • 79bc193 Merge pull request #2510 from karma-runner/greenkeeper-useragent-2.1.10
  • e89f092 Merge pull request #2527 from karma-runner/greenkeeper-qunitjs-2.1.1
  • 85beac2 Merge pull request #2530 from karma-runner/greenkeeper-eslint-plugin-react-6.9.0
  • daeb31e Merge pull request #2531 from karma-runner/greenkeeper-grunt-auto-release-0.0.7
  • ea40f15 chore(package): update grunt-auto-release to version 0.0.7
  • 495ab0c chore(package): update eslint-plugin-react to version 6.9.0
  • c20d004 chore(package): update qunitjs to version 2.1.1
  • 13cefee Merge pull request #2503 from karma-runner/greenkeeper-eslint-3.12.1
  • c9a3a63 docs(config): add jsdom to the browser launchers list

There are 42 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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jan 14, 2017

After pinning to 1.3.0 your tests are passing again. Downgrade this dependency 📌.

Munter added a commit that referenced this issue Jan 18, 2017
limit browser concurrency on sauce; closes #2478 and #2667
sgilroy pushed a commit to TwineHealth/mocha that referenced this issue Feb 27, 2019
limit browser concurrency on sauce; closes mochajs#2478 and mochajs#2667
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant