Open redbaron opened 3 years ago
Thanks for the report. I'll need to check exactly what is going on here, but I agree this is pretty undesirable behaviour.
com.ovoenergy:rac-gas-loss
👀 say hello to Monty and the rest of the R&C gang from me!
@cb372 I've just hit the same on a fairly large project - and given that plugin compares the whole module ID, you need to always have your version pinned to the latest (as decided by eviction), otherwise you get this.
What makes it difficult is that if you have a Scala Steward setup, then you have the following:
PR 2 will be failing because it pins CE to previous latest, but it gets evicted - so this plugin is angry PR 1 needs to go in first, and PR2 will need to be rebased.
Would you accept a PR that compares dependencies without taking the actual version into account? just org name and module name
In one of the projects I have declared libraryDependency
"co.fs2" %% "fs2-core" % "0.10.5"
.It is then evicted like following:
Which makes it both unused and undeclared from this plugin perspective:
Technically it is true, but dependency eviction is unavoidable in any big enough project, which makes use of this plugin in CI pipelines impossible as it reports errors in cases like this.