littlerobots / version-catalog-update-plugin

Gradle plugin for updating a project version catalog
Apache License 2.0
565 stars 23 forks source link

Particular libraries are getting downgraded #118

Open extmkv opened 1 year ago

extmkv commented 1 year ago

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

hvisser commented 1 year ago

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 commented 11 months ago

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!

beshoy-samy commented 7 months ago

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

hvisser commented 7 months ago

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