-
Notifications
You must be signed in to change notification settings - Fork 0
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-test is breaking the build 🚨 #13
Comments
After pinning to 1.6.0 your tests are passing again. Downgrade this dependency 📌. |
Version 1.7.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 1.7.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 1.8.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv1.8.0Add capacity to define namespace and resolved path to stubbed generators. |
Version 1.9.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv1.9.0
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 💪
Status Details
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 and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: