-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Version 0.4.1 is a breaking change #116
Comments
I have the same issue (see 01mf02/jaq#176 and 01mf02/jaq#178): yansi 1.0 is a breaking change compared to yansi 0.5, so because ariadne 0.4 exposes types from yansi 0.5, ariadne 0.4.1 cannot depend on yansi 1.0. A solution to this problem would be to yank the 0.4.1 release and publish a 0.5 release instead. |
@zesterer, may I ask you if there is any update on this? Builds of my application still break due to this issue. |
Argh, this is annoying. Apologies about that. Sorry, I've not had much time to focus on this of late. I'll try to get this resolved over the next few days. |
Thanks. Btw, to catch this kind of issues in advance, |
It removed the
ariadne::Color::Default
variant, so my project fails to compile. It should be a minor release, not a patch one, becausecargo
will pull the new version even if I depended on0.4
.The text was updated successfully, but these errors were encountered: