Update karma-chrome-launcher to version 2.1.1 🚀 #100
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
karma-chrome-launcher just published its new version 2.1.1.
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
Bug Fixes
The new version differs by 40 commits .
f61d786chore: release v2.1.1253f168chore: update contributors0db9489Merge pull request #124 from cexbrayat/feat/disable-renderer-backgrounding6bfc170fix: add disable-renderer-backgrounding flag5b5b4aeMerge pull request #121 from karma-runner/add-supported-browsers-infoaa5b581docs: add supported browsers list2267df1chore: release v2.1.0f993c48chore: update contributors7446181feat: add support for headless Chrome/ChromeCanaryd81da0eMerge pull request #116 from maieutiquer/patch-137513a9clean-up irrelevant commenta0235a2Merge pull request #115 from karma-runner/greenkeeper-standard-10.0.08987630chore(package): update standard to version 10.0.01e4b4ffMerge pull request #110 from karma-runner/greenkeeper-standard-9.0.25d559e7chore(package): update standard to version 9.0.2There are 40 commits in total. See the full diff.