An in-range update of yeoman-test is breaking the build 🚨
greenkeeper opened this issue · comments
☝️ 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 devDependency yeoman-test was updated from 2.2.0 to 2.3.0.
This version is covered by your current version range and after updating it in your project the build failed.
yeoman-test 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/travis-ci/push: The Travis CI build failed (Details).
Release Notes for Release v2.3.0
- Passes localConfigOnly to generators by default.
- Update dependencies.
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 🌴
After pinning to 2.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependencyyeoman-test was updated from2.4.0to2.4.1.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀
Release Notes for Release v2.4.1
- Revert breaking change.
- The
devDependencyyeoman-test was updated from2.4.1to2.5.0.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀
Release Notes for Release v2.5.0
- Add environment options to run method.
- The
devDependencyyeoman-test was updated from2.5.0to2.6.0.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀
Release Notes for Release v2.6.0
- Add environment centric test.
- Fixes