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.
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.
8686681Merge pull request #2297 from Dam-ien/fixHtmlEncoded
da1930ffix(web-server): Allow karma to run in project which path contains HTML URL encoded characters. Karma fails on Jenkins when it checks out branches containing '/' as it converts it to '%2F'. Fixes errors seen on #1751, #61.
e5d792dMerge pull request #2226 from TheModMaker/feat/range-requests
There are 250 commits in total. See the full diff.
Coverage remained the same at 85.271% when pulling c84a65ce16445bcf81a5b2cd0c96fd21d50ccf19 on greenkeeper-karma-1.3.0 into 466d5b4eb12edde46576ad72008921644cbd72a9 on 1.x.x.
Hello lovely humans,
karma just published its new version 1.3.0.
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. 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 :sparkles:
You rock!
:palm_tree:
GitHub Release
Bug Fixes
Features
The new version differs by 757 commits (ahead by 757, behind by 2).
9cd65cd
chore: release v1.3.0
b22430b
chore: update contributors
1e822a5
Merge pull request #2212 from pghalliday/feature-upstream-proxy
55755e4
feat: upstreamProxy config option to deal with proxies that adjust the base path, etc
98a4fbf
feat(reporter): add config formatError function
96f8f14
fix(launcher): exclude concurrent browser on launcher restart
173ee47
Merge pull request #2326 from SteveVanOpstal/patch-1
696123b
docs(gh): fix typos
ee6ba49
Merge pull request #2315 from kahwee/fix-range
8b1b4b1
fix(middleware): ensure Range headers adhere more closely to RFC 2616
322f3b3
chore: release v1.2.0
4e511ef
chore: update contributors
8686681
Merge pull request #2297 from Dam-ien/fixHtmlEncoded
da1930f
fix(web-server): Allow karma to run in project which path contains HTML URL encoded characters. Karma fails on Jenkins when it checks out branches containing '/' as it converts it to '%2F'. Fixes errors seen on #1751, #61.
e5d792d
Merge pull request #2226 from TheModMaker/feat/range-requests
There are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade