nickschot / lux-jwt

Middleware implementation of JWT for Lux.
MIT License
15 stars 1 forks source link

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

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 10.1.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 10.0.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 - ❌ **coverage/coveralls** Coverage pending from Coveralls.io [Details](https://coveralls.io/builds/9717875) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/nickschot/lux-jwt/builds/192899969)
Commits

The new version differs by 14 commits .

  • 8f7af3a chore(release): 10.1.0
  • 8c58d68 fix: address edge-cases related to --all when instrumentation is disabled (#482)
  • 8b58c05 feat: allow eager instantiation of instrumenter (#490)
  • d8d2de0 feat: upgrade to istanbul-lib-instrument with support for 'const foo = function () {}' name preservation. upgrade to istanbul-lib-hook with fix for ts-node. (#494)
  • 7708235 chore: add test and docs for high and low watermarks (#493)
  • 0a1d72a feat: reporting watermarks can now be set in nyc config stanza (#469)
  • 1022b16 fix: pass configuration options to --check-coverage (#483)
  • 7b4c090 chore(package): update tap to version 9.0.3 (#488)
  • 093963b chore(release): 10.0.2
  • e01ec8c fix: upgrade to newer istanbul-lib-instrument, with fixes for inferred function names (#479)
  • 2e39e00 chore(release): 10.0.1
  • e0ef1d5 fix: upgrade spawn-wrap and istanbul-lib-instrument (#477)
  • 8603aa9 chore(package): update is-windows to version 1.0.0 (#466)
  • 64ae4f3 chore(package): update standard-version to version 4.0.0 (#461)

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 10.0.0 your tests are passing again. Downgrade this dependency πŸ“Œ.

greenkeeper[bot] commented 7 years ago

Version 10.1.2 just got published.

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

Commits

The new version differs by 4 commits .

  • e46335f chore(release): 10.1.2
  • 25aec77 fix: revert defaulting to empty file-coverage report, this caused too many issues
  • e03cd48 chore(release): 10.1.1
  • 81229a0 fix: fix bug related to merging coverage reports see #482

See the full diff.