Open greenkeeper[bot] opened 7 years ago
Your tests are still failing with this version. Compare the changes π¨
The new version differs by 4 commits0.
e062a86
chore(release): 10.3.2
213206f
fix: we should not create a cache folder if cache is false (#567)
75713d8
chore(release): 10.3.1
1bf74fd
fix: introduced a bug that resulted in source-maps not being loaded approriately on second test run (#566)
false
See the full diff
Your tests are passing again with this version. Explicitly upgrade to this version π
The new version differs by 22 commits.
a3f033f
chore(release): 11.1.0
a076951
chore: upgrade to latest version of istanbul-lib-instrument
8768afe
feat: upgrade to version of spawn-wrap that supports .EXE (#626)
2d92501
chore: attempt to fix appveyor (#623)
bbadc1f
feat: add support for per file coverage checking (#591)
e9fad9f
docs: add note about tap-nyc to README (#614)
f86b0b1
chore(release): 11.0.3
923b062
fix: upgrade to spawn-wrap version that works with babel-register (#617)
b1eb4d6
fix: update help link to list of reporters (#601)
e4eff12
chore(release): 11.0.2
0c2ef43
chore: upgrade to newer version of spawn-wrap (#592)
9d47986
chore(release): 11.0.1
fa1097a
chore: acutally swap in new copy of signals.js
8662357
chore: hack to fix SIGPROF binding issue on node 8
d90aed6
chore(release): 11.0.0
There are 22 commits in total.
See the full diff
Your tests are still failing with this version. Compare the changes π¨
The new version differs by 29 commits.
b2ff72d
chore(release): 11.2.0
97b962e
chore: explicit update of istanbul-lib-instrument (#662)
0dcceda
feat: allow cwd to be configured see #620
0fc6d8f
chore: add support for --cwd (#542) (#620)
658dba4
fix: remove excluded files from coverage before writing (#649)
dd40dc5
feat: add possibility to filter coverage-maps (#637)
fb3ab92
docs: add link to community slack (#639)
a3f033f
chore(release): 11.1.0
a076951
chore: upgrade to latest version of istanbul-lib-instrument
8768afe
feat: upgrade to version of spawn-wrap that supports .EXE (#626)
2d92501
chore: attempt to fix appveyor (#623)
bbadc1f
feat: add support for per file coverage checking (#591)
e9fad9f
docs: add note about tap-nyc to README (#614)
f86b0b1
chore(release): 11.0.3
923b062
fix: upgrade to spawn-wrap version that works with babel-register (#617)
There are 29 commits in total.
See the full diff
Your tests are still failing with this version. Compare the changes π¨
Your tests are passing again with this version. Explicitly upgrade to this version π
The new version differs by 12 commits.
d85118c
chore(release): 11.3.0
7792733
chore: explicitly update istanbul dependencies (#698)
222a3d0
chore: slight difference in pinning logic, based on @ljharb's advice
f04b7a9
feat: add option to hook vm.runInContext (#680)
cdfdff3
feat: add --exclude-after-remap option for users who pre-instrument their codebase (#697)
a413f6a
chore: upgrade to yargs 10 (#694)
10125aa
docs: fix reporters link
f5089ca
docs: added examples of coverage reports (#656)
af281e7
chore: update spawn-wrap to 1.4.0 (#692)
a685f7c
docs: missing options prefix -- in front of check-coverage (#695)
f31d7a6
feat: allow instrument-only to produce sourcemaps (#674)
425c0fd
chore: ignore package-lock.json (#683)
See the full diff
Version 10.3.0 of nyc just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As nyc is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this :muscle:
Status Details
- β **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/timdp/winston-aws-cloudwatch/build/301)Commits
The new version differs by 4 commits ahead by 4, behind by 2.
55e826d
chore(release): 10.3.0
89dc7a6
chore: explicit update of istanbul dependnecies (#562)
1887d1c
feat: add support for --no-clean, to disable deleting raw coverage output (#558)
ff73b18
fix: source-maps were not being cached in the parent process when --all was being used (#556)
false
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: