-
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 meteor-node-stubs is breaking the build 🚨 #118
Comments
Version 0.2.6 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 0.2.7 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 0.2.8 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 0.2.9 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 7 commits.
See the full diff |
Version 0.2.10 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 0.2.11 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 0.2.5 of meteor-node-stubs just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As meteor-node-stubs is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Status Details
Commits
The new version differs by 2 commits .
618d671
Bump NPM version to 0.2.5 in preparation for publishing.
e22136d
Avoid calling require.resolve at runtime.
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: