Open greenkeeper[bot] opened 7 years ago
After pinning to 1.6.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
Add capacity to define namespace and resolved path to stubbed generators.
Your tests are still failing with this version. Compare the changes 🚨
This fix could break some users tests - but these tests should've been failing as the generator itself would be throwing an exception.
Version 1.7.0 of yeoman-test just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As yeoman-test is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/zguillez/generator-starling/builds/251669044?utm_source=github_status&utm_medium=notification)Release Notes
v1.7.0Commits
The new version differs by 3 commits.
3c83d8f
1.7.0
71ca3b3
Bump dependencies
ccbf848
Update dependencies to enable Greenkeeper 🌴 (#28)
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: