-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Particular libraries are getting downgraded #118
Comments
This has been mentioned a couple of times, for example here: #116 Can you try if running the task with This plugin uses the report from the dependency versions plugin, and if that report "downgrades" the dependency, it wil reflect in the TOML file. If you can provide the report.json that would be helpful too, as it lists what the current versions are according to that plugin. |
The 0.8.2 release has a new way of resolving dependencies, which might fix this problem too (see #125 for more details). Would be great if you could try it on your project! |
Hey coming back to this even with the current version |
@beshoy-samy did you enable the new resolver? Like mentioned in #125? If you want me to take a look, please provide a minimal project as an example that reproduces the problem. |
Describe the issue
Particular libraries are getting downgraded, even if on the TOML it says there's a new update available.
Attached you can see the libraries that are being downgraded.
com.google.android.play:core
always downgraded to 1.8.0 from 1.10.3ok.squareup.okhttp3:okhttp
downgraded to 4.9.2 from 4.11.0Stacktrace
Please run Gradle with the
--stacktrace
option and share the output in case of a Gradle error.The text was updated successfully, but these errors were encountered: