You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This version is covered by your current version range and after updating it in your project the build failed.
As mukla 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
❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Version 0.4.9 of mukla just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As mukla 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
❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 6 commits .
a895cc4
chore(release): 0.4.9
b93c4d4
fix(readme): update readme template
d036e6f
fix(ci): update CI and add appveyor
4d00b3c
fix(package): update deps and npm scripts
3992991
fix(package): use stacktrace-metadata for better reporter
4b7ad36
chore(package): remove lazy-cache
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: