This message was deleted.

In the past, when a transitive required a higher version of a dependency but then was later deselected, Gradle never downgraded the transitive. When we introduced that behaviour, we hit a couple problematic graphs where dependency cycles resulted in a dependency alternating between two versions. And each time you select a version it causes the other one to be a better answer. This led to never ending resolution. So as a protection against this, we now stop downgrading a dependency after it has changed version a 1000 times. And we print the warning you have seen to let users know that their graph is unstable. If you know the version you are supposed to get, you could attempt adding a

strictly

constraint and see what happens. Otherwise you may need to figure out what is happening and constraint one of the edges playing in the cycle.

thank you!