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 ansi-escapes is breaking the build 🚨 #337

Closed
greenkeeper bot opened this issue Nov 16, 2019 · 2 comments
Closed

An in-range update of ansi-escapes is breaking the build 🚨 #337

greenkeeper bot opened this issue Nov 16, 2019 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Nov 16, 2019

The dependency ansi-escapes was updated from 4.2.1 to 4.3.0.

🚨 View failing branch.

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

ansi-escapes 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
  • Test on node 12.x and macOS-latest: null
  • Test on node 12.x and windows-latest: null
  • Test on node 12.x and ubuntu-latest: null
  • Test on node 10.x and macOS-latest: null
  • Test on node 10.x and windows-latest: null
  • Test on node 10.x and ubuntu-latest: null
  • Test on node 8.12.x and macOS-latest: null
  • Test on node 8.12.x and windows-latest: null
  • Test on node 8.12.x and ubuntu-latest: null

Release Notes for v4.3.0

v4.2.1...v4.3.0

Commits

The new version differs by 3 commits.

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 Nov 16, 2019

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

@agilgur5
Copy link
Collaborator

agilgur5 commented Mar 9, 2020

This was probably failing due to the intermittent persistent CI errors that #504 fixed.

@agilgur5 agilgur5 closed this as completed Mar 9, 2020
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

1 participant