Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
greenkeeper bot opened this issue Jun 1, 2020 · 1 comment
Closed

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

greenkeeper bot opened this issue Jun 1, 2020 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jun 1, 2020


🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io


The devDependency nyc was updated from 15.0.1 to 15.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

nyc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: build: Your tests passed on CircleCI! (Details).
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 5 commits.

  • de7baa4 chore(release): 15.1.0
  • 992359a feat(experimental): Support using --all with node.js ESM (#1320)
  • 086fd20 chore: Regenerate package-lock, update source-map-support test (#1314)
  • b20f751 chore: add bugs (used, e.g., by npmjs) (#1313)
  • 6898e88 chore: Fix CHANGELOG.md version header

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jun 1, 2020

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

@greenkeeper greenkeeper bot closed this as completed Jun 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants