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 cross-env is breaking the build 🚨 #59

Open
greenkeeper bot opened this issue Aug 31, 2019 · 1 comment
Open

An in-range update of cross-env is breaking the build 🚨 #59

greenkeeper bot opened this issue Aug 31, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Aug 31, 2019

The dependency cross-env was updated from 5.2.0 to 5.2.1.

🚨 View failing branch.

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

cross-env 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
  • continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
  • continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Release Notes for v5.2.1

5.2.1 (2019-08-31)

Bug Fixes

Commits

The new version differs by 6 commits.

  • a75fd0e fix: remove is-windows dependency (#207)
  • 4889923 docs: add note for windows issues
  • 2b36bb3 docs: add Jason-Cooke as a contributor (#201)
  • 41ab3b0 docs: Fix typo (#200)
  • 553705c docs(README): list @naholyr/cross-env in Other Solutions section (#189)
  • 5d0f19f docs: remove codesponsor (#186)

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 Aug 31, 2019

After pinning to 5.2.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