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 yeoman-generator is breaking the build 🚨 #303

Open
greenkeeper bot opened this issue Apr 9, 2020 · 1 comment
Open

An in-range update of yeoman-generator is breaking the build 🚨 #303

greenkeeper bot opened this issue Apr 9, 2020 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Apr 9, 2020


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The dependency yeoman-generator was updated from 4.7.2 to 4.8.0.

🚨 View failing branch.

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

yeoman-generator 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 failed (Details).

Release Notes for Release v4.8.0
  • Fix security warning.
  • Any emitted error rejects #run promise.
  • Implement cancellable tasks. (#1204)
  • Add option to forward errors to the environment.
  • Make yeoman-environment and mem-fs-editor dependency optional.
  • Implement conflicter predefined status (#1210)
  • Allow decoupling generator's and composed generator's cwd from env cwd.
  • Implement checkEnvironmentVersion
  • Fixes.
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 Apr 9, 2020

After pinning to 4.7.2 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