search

xiangst0816 / blog

Thoughts, stories and ideas.
https://xiangst0816.github.io/blog/
MIT License
4 stars 0 forks source link

An in-range update of shelljs is breaking the build 🚨 #44

Closed greenkeeper[bot] closed 1 year ago

greenkeeper[bot] commented 5 years ago

The devDependency shelljs was updated from 0.8.2 to 0.8.3.

🚨 View failing branch.

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

shelljs 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/xiangsongtao/blog/builds/454318138?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 20 commits.

  • d4d1317 0.8.3
  • db317bf Add test case for sed on empty file (#904)
  • 0d5ecb6 docs(changelog): updated by Nate Fischer [ci skip]
  • 6b3c7b1 refactor: don't expose tempdir in common.state (#903)
  • 4bd22e7 chore(ci): fix codecov on travis (#897)
  • 2b3b781 fix: silent exec (#892)
  • 37acb86 chore(npm): add ci-or-install script (#896)
  • 4e861db chore(appveyor): run entire test matrix (#886)
  • d079515 docs: remove gitter badge (#880)
  • 4113a72 grep includes the i flag (#876)
  • 8dae55f Fix(which): match only executable files (#874)
  • 6d66a1a chore: rename some tests (#871)
  • 131b88f Fix cp from readonly source (#870)
  • 1dd437e fix(mocks): fix conflict between mocks and skip (#863)
  • 72ff790 chore: bump dev dependencies and add package-lock (#864)

There are 20 commits in total.

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 5 years ago

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