Closed greenkeeper[bot] closed 6 years ago
Update to this version instead π
The new version differs by 5 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)
See the full diff
Update to this version instead π
The new version differs by 7 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)
See the full diff
Update to this version instead π
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
Update to this version instead π
The new version differs by 13 commits.
b473820
chore(release): 11.4.1
4e4f428
fix: explicitly update spawn-wrap (#748)
456fa20
docs: hide the header in the issue template on render [skip ci] (#731)
e8225d5
chore(release): 11.4.0
93efc55
chore: upgrading to newer spawn-wrap (#730)
879631a
refactor: slight tweak to how we extract the --nycrc-path
785fccb
feat: allow alternate path for .nycrc to be specified (#724)
4ff7a38
docs: fix package.json examples: s/script/scripts (#722)
9f2894f
chore: babel-preset-es2015 => babel-preset-env (#705)
2dee543
docs: correct check-coverage shorthand example (#715)
7ea96ba
fix: always invoke instrumenter callback, set appropriate exit-code (#703)
7294308
docs: Correct examples in README.md (#702)
6286bf8
docs: update exclude defaults (#701)
See the full diff
Version 11.0.1 of nyc just got published.
The version 11.0.1 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 nyc. 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 11 commits.
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
2f68559
chore: hack to prevent SIGPROF warning, until new spawn-wrap is available
f18f780
fix: add support for ES6 modules
0e6b277
chore: formatting nit
80ef0a3
docs: mention the ability to publish configuration in docs
33829b8
feat: upgrade to version of yargs with support for presets
55b68b5
chore: update istanbuljs dependencies (#583)
a1a457f
feat: allow .nycrc.json (#580)
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: