-
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 nano is breaking the build 🚨 #15
Labels
Comments
Version 6.4.2 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 |
Version 6.4.3 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 15 commits.
See the full diff |
Version 6.4.4 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 25 commits.
There are 25 commits in total. See the full diff |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version 6.4.1 of nano just got published.
This version is covered by your current version range and after updating it in your project the build failed.
nano 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
Release Notes
6.4.1Switch to
cloudant-follow
dependency.Commits
The new version differs by 4 commits ahead by 4, behind by 1.
56a5470
6.4.1
c0c4558
6.4.0 mismatch
f503170
Merge pull request #51 from apache/feat/cloudant-follow
0de43ee
feat: switch from follow to cloudant-follow, which is maintaned
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: