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 eslint-config-standard is breaking the build 🚨 #49

Open
greenkeeper bot opened this issue Mar 20, 2020 · 1 comment
Open

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Mar 20, 2020


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency eslint-config-standard was updated from 14.1.0 to 14.1.1.

🚨 View failing branch.

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

eslint-config-standard 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 failed on CircleCI (Details).

Commits

The new version differs by 7 commits.

  • 3f4a3fe 14.1.1
  • 2a14319 Merge pull request #164 from standard/remove-no-return-await
  • 243d38f Remove no-return-await rule
  • eb187de chore: .npmrc with package-lock=false (#155)
  • dcf95fe chore: .npmrc with package-lock=false
  • e5e81a8 Merge pull request #153 from standard/greenkeeper/eslint-plugin-node-10.0.0
  • 83ba3be chore(package): update eslint-plugin-node to version 10.0.0

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 Mar 20, 2020

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

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