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-spec-reporter.
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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
karma-spec-reporter just published its new version 0.0.31.
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-spec-reporter. 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:
The new version differs by 34 commits .
ed403e7
chore(packageJSON): bump for new patch
37be064
Merge pull request #64 from fluffynuts/master
26247ab
fix: explicitly depend on mocha
b4a0ca8
fix: require at least node v4 to run on travis (npm-run-all wants it and istanbul is failing to find _mocha)
0e0f30b
fix: add coverage for final error reporting
92d66fe
fix: allow test prefixes to be overridden on win32
dac41c0
fix: undo workaround for color output on windows; test passes now
d4a5aff
fix: update test and coverage npm scripts
404cb09
chore(packageJSON): bump for new patch
ff5c847
chore(branch): Merge branch 'PetroCloud-master'
0265a8a
chore(branch): Merge branch 'master' of https://github.com/PetroCloud/karma-spec-reporter into PetroCloud-master
34ab2ba
chore(branch): Merge branch 'windows'
5f44cf3
Merge pull request #58 from souvikbasu/master
49a3e65
test(reporter): test failing for color config on windows
47e3b53
chore(branch): bump for patch
There are 34 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.