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-spawn is breaking the build 🚨 #1279

Closed
greenkeeper bot opened this issue Jan 31, 2018 · 1 comment
Closed

An in-range update of cross-spawn is breaking the build 🚨 #1279

greenkeeper bot opened this issue Jan 31, 2018 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

@greenkeeper greenkeeper bot commented Jan 31, 2018

Version 6.0.4 of cross-spawn was just published.

Branch Build failing 🚨
Dependency cross-spawn
Current Version 6.0.3
Type devDependency

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

cross-spawn 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/appveyor/branch AppVeyor build succeeded Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 3 commits.

  • 52e557e chore(release): 6.0.4
  • 6f43a61 Merge pull request #91 from moxystudio/fix-unix-path-normalize
  • 06ee3c6 fix: fix paths being incorrectly normalized on unix

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 greenkeeper bot added the greenkeeper label Jan 31, 2018
@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

@greenkeeper greenkeeper bot commented Jan 31, 2018

After pinning to 6.0.3 your tests are passing again. Downgrade this dependency 📌.

@lock lock bot locked as resolved and limited conversation to collaborators May 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.