Skip to content
This repository has been archived by the owner on Mar 6, 2018. It is now read-only.

Update karma-chrome-launcher to version 2.0.0 🚀 #54

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

karma-chrome-launcher just published its new version 2.0.0.

State Update 🚀
Dependency karma-chrome-launcher
New version 2.0.0
Type devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of karma-chrome-launcher.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴


GitHub Release

Features

  • Chromium support for Linux, Darwin and Windows (33e8d82)

The new version differs by 5 commits .

  • 4110f87 chore: release v2.0.0
  • a5a7b40 chore: update contributors
  • 33e8d82 feat: Chromium support for Linux, Darwin and Windows
  • 108cd87 Merge pull request #72 from sudavid4/master
  • 5337b94 fix:disable new printer notification

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

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

Successfully merging this pull request may close these issues.

2 participants