motss/deep.clone

An in-range update of nyc is breaking the build 🚨

Closed this issue Β· 3 comments

Version 11.2.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.1.0
Type devDependency

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 πŸ’ͺ

Status Details
  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/nyc-11.2.0 at 100.0% Details

Commits

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

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

After pinning to 11.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

Version 11.2.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 3 commits.

  • 87281f9 chore(release): 11.2.1
  • 3bd1527 fix: create temp directory when --no-clean flag is set #663 (#664)
  • a10d478 fix: apply exclude logic before remapping coverage (#667)

See the full diff

Version 11.3.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version πŸš€

Commits

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