search

asset-pipe / integration

Integration verification module
Other
0 stars 0 forks source link

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

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 4.13.1 of eslint was just published.

Branch Build failing 🚨
Dependency eslint
Current Version 4.13.0
Type devDependency

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

eslint 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 - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/asset-pipe/integration/builds/315092542?utm_source=github_status&utm_medium=notification)
Release Notes v4.13.1
  • b72dc83 Fix: eol-last allow empty-string to always pass (refs #9534) (#9696) (Kevin Partington)
  • d80aa7c Fix: camelcase destructure leading/trailing underscore (fixes #9700) (#9701) (Kevin Partington)
  • d49d9d0 Docs: Add missing period to the README (#9702) (Kevin Partington)
  • 4564fe0 Chore: no-invalid-meta crash if no export assignment (refs #9534) (#9698) (Kevin Partington)
Commits

The new version differs by 6 commits.

  • 234cd26 4.13.1
  • 3b0833f Build: changelog update for 4.13.1
  • b72dc83 Fix: eol-last allow empty-string to always pass (refs #9534) (#9696)
  • d80aa7c Fix: camelcase destructure leading/trailing underscore (fixes #9700) (#9701)
  • d49d9d0 Docs: Add missing period to the README (#9702)
  • 4564fe0 Chore: no-invalid-meta crash if no export assignment (refs #9534) (#9698)

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 6 years ago

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

SimenB commented 6 years ago

Just test timeouts, nothing to do with the eslint upgrade