Open greenkeeper[bot] opened 7 years ago
Update to this version instead π
The new version differs by 5 commits .
34ab2ba
chore(branch): Merge branch 'windows'
5f44cf3
Merge pull request #58 from souvikbasu/master
49a3e65
test(reporter): test failing for color config on windows
d20a0b3
Fixed failing test for prefix symbol change
02c7083
Added space after prefix symbol for Windows platform
See the full diff.
Update to this version instead π
The new version differs by 7 commits .
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
03abf3d
remove old extra added param
cb57123
Make use of karma setting for browser log
4ca96c6
updates README.md
7323bef
Adds supressBrowserLog option
See the full diff.
Update to this version instead π
The new version differs by 8 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
See the full diff.
Update to this version instead π
The new version differs by 5 commits.
a1a63b7
chore(packageJSON): bump for new patch
5a513f3
Merge pull request #73 from joshuaegclark/color-fix
51a677c
fix(colors): Set colors.enabled = true when colors is defined
0ba0bbc
Merge pull request #70 from sudo-suhas/ci_multi_node_ver
d1e79f8
ci: Run tests on multiple node versions
See the full diff
Version 0.0.27 of karma-spec-reporter just got published.
The version 0.0.27 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.
Commits
The new version differs by 4 commits .
10f5306
chore(packageJSON): bump for patch
bab52ef
Merge pull request #63 from kentrino/feat/fast_fail
795cae1
feat(reporter) add fail fast option
a71f679
Create License.md
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: