search

bitjson / typescript-starter

Quickly create and configure a new library or Node.js project
https://bitjson.github.io/typescript-starter/
MIT License
3.48k stars 245 forks source link

An in-range update of execa is breaking the build 🚨 #209

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 5 years ago

The dependency execa was updated from 2.0.4 to 2.0.5.

🚨 View failing branch.

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

execa is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ✅ **ci/circleci: node-latest:** Your tests passed on CircleCI! ([Details](https://circleci.com/gh/bitjson/typescript-starter/858?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)). - ✅ **continuous-integration/travis-ci/push:** The Travis CI build passed ([Details](https://travis-ci.org/bitjson/typescript-starter/builds/593424955?utm_source=github_status&utm_medium=notification)). - ✅ **ci/circleci: node-10:** Your tests passed on CircleCI! ([Details](https://circleci.com/gh/bitjson/typescript-starter/857?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)). - ❌ **continuous-integration/appveyor/branch:** AppVeyor build failed ([Details](https://ci.appveyor.com/project/bitjson/typescript-starter/builds/27875103)).
Release Notes for v2.0.5

Bug fixes

  • Make execa compatible with Node.js 13.0.0-pre (#370) d268fd1

v2.0.4...v2.0.5

Commits

The new version differs by 2 commits.

  • 603537a 2.0.5
  • d268fd1 Make execa compatible with Node.js 13.0.0-pre (#370)

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 2.0.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 6 commits.

  • e98561a 2.1.0
  • c6a24ec Add error.originalMessage property (#373)
  • f9bd317 Upgrade cross-spawn to 7.0.0 (#367)
  • f620305 Document the reasons why the returned promise might fail (#364)
  • 7c19345 Revert "Add a sentence about job search (#293)" (#352)
  • 48067c4 Properly clean up child processes created during tests (#349)

See the full diff