search

Kronos-Integration / interceptor-object-data-processor-chunk

process and check import data streams. This checks the aggregated data
BSD 2-Clause "Simplified" License
1 stars 0 forks source link

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

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 11.2.1 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.2.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 :muscle:

Status Details - ❌ **bitHound - Code** 3 failing files. [Details](https://www.bithound.io/github/Kronos-Integration/kronos-interceptor-object-data-processor-chunk/f21273961fd72fb3d9efba98e1615e5fa8748825/files#filter-failing-file) - ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/Kronos-Integration/kronos-interceptor-object-data-processor-chunk/f21273961fd72fb3d9efba98e1615e5fa8748825/dependencies/npm?status=passing) - ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/Kronos-Integration/kronos-interceptor-object-data-processor-chunk/builds/272374483?utm_source=github_status&utm_medium=notification) - ✅ **codecov/patch** Coverage not affected when comparing 5796de4...f212739 [Details](https://codecov.io/gh/Kronos-Integration/kronos-interceptor-object-data-processor-chunk/commit/f21273961fd72fb3d9efba98e1615e5fa8748825) - ✅ **codecov/project** 83.92% remains the same compared to 5796de4 [Details](https://codecov.io/gh/Kronos-Integration/kronos-interceptor-object-data-processor-chunk/commit/f21273961fd72fb3d9efba98e1615e5fa8748825)
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

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:

greenkeeper[bot] commented 7 years ago

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