version-catalog-update-plugin icon indicating copy to clipboard operation
version-catalog-update-plugin copied to clipboard

Particular libraries are getting downgraded

Open extmkv opened this issue 2 years ago • 4 comments

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.3 ok.squareup.okhttp3:okhttp downgraded to 4.9.2 from 4.11.0

Stacktrace Please run Gradle with the --stacktrace option and share the output in case of a Gradle error. Screenshot 2023-09-14 at 10 29 08 Screenshot 2023-09-14 at 10 35 02

extmkv avatar Sep 14 '23 08:09 extmkv

This has been mentioned a couple of times, for example here: https://github.com/littlerobots/version-catalog-update-plugin/issues/116

Can you try if running the task with --refresh-dependencies helps? I suspect this is some kind of sorting issue in the dependency versions plugin, but I'm not sure. If you have a project that you can provide that reproduces this consistently, that would be great.

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.

hvisser avatar Sep 14 '23 16:09 hvisser

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!

hvisser avatar Dec 22 '23 09:12 hvisser

Hey coming back to this even with the current version 0.8.4 issue is still happening

beshoy-samy avatar Apr 18 '24 15:04 beshoy-samy

@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.

hvisser avatar Apr 18 '24 16:04 hvisser