jhwohlgemuth/applied

An in-range update of karma-firefox-launcher is breaking the build 🚨

greenkeeper opened this issue · 0 comments

greenkeeper commented

Version 1.0.1 of karma-firefox-launcher just got published.

Branch Build failing 🚨
Dependency karma-firefox-launcher
Current Version 1.0.0
Type devDependency

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

As karma-firefox-launcher 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 is in progress Details

  • ❌ bitHound - Code 7 failing files. Details

  • ✅ bitHound - Dependencies No failing dependencies. Details

Commits

The new version differs by 10 commits .

  • 2143fd2 chore(release): 1.0.1
  • e3eddff Merge pull request #66 from karma-runner/cleanup
  • 5bbf5c3 style: lint happy
  • e68a711 docs(readme): add badges
  • 92cc77c refactor: clean up code and add tests
  • 3ffa514 fix: only use $HOME environmental variable if it exists
  • 9f28aa9 fix: disable multi-process firefox
  • 1339149 Merge pull request #53 from markchagers/fix-windows-launch
  • 3322a61 fix(windows): change getFirefoxExe function to find exe on other drive
  • a332915 fix(windows): change getFirefoxExe function to allow running on win64

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 🌴