search

jonathanweiss / component-manager

Micro utility (583 bytes compressed) that manages initialising and teardown of components (e.g. jQuery plugins) as soon as specific DOM nodes are added into the document, respectively removed from it.
MIT License
7 stars 0 forks source link

An in-range update of karma-sauce-launcher is breaking the build 🚨 #74

Open greenkeeper[bot] opened 7 years ago

greenkeeper[bot] commented 7 years ago

Version 1.2.0 of karma-sauce-launcher just got published.

Branch Build failing 🚨
Dependency karma-sauce-launcher
Current Version 1.1.0
Type devDependency

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

As karma-sauce-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 :muscle:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/jonathanweiss/component-manager/builds/267162851?utm_source=github_status&utm_medium=notification)
Release Notes v1.2.0

Features

  • config: add proxy option (bae758a)
  • config: allow SE traffic to be sent via Sauce Connect's Relay (0ac67d4)
  • config: pass parentTunnel to selenium (bae326f)
  • deps: upgrade sauce connect (e792677)
  • launcher: expose commandTimeout, idleTimeout, maxDuration options (3fe1c75), closes #62
Commits

The new version differs by 13 commits.

  • 004d61d chore: release v1.2.0
  • f783f63 chore: update contributors
  • a21fbd9 chore(deps): update dev dependencies
  • 79c70c2 feat(config): expose commandTimeout, idleTimeout, maxDuration options
  • f607303 Merge branch 'master' of https://github.com/JamieMason/karma-sauce-launcher into JamieMason-master
  • 0362ad5 docs(readme): fix SauceLabs doc links
  • 0ac67d4 feat(config): allow SE traffic to be sent via Sauce Connect's Relay
  • 0219065 docs(readme): add hint to platform configurator
  • bae326f feat(config): pass parentTunnel to selenium
  • bae758a feat(config): add proxy option
  • e792677 feat(deps): upgrade sauce connect
  • 79b688c chore(travis): update build config
  • 3fe1c75 feat(launcher): expose commandTimeout, idleTimeout, maxDuration options

See the full diff

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

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