I would stop publishing the BOM (even now, we don't have to wait for this issue to be addressed). Lots of other things to focus on.
I'd publish it in the upcoming version say that this would potentially be the last release of the detekt-bom artifact. This would allow us to understand if there are strong concerns or users depending heavily on it.
Originally posted by @cortinico in #3688 (comment)
Just a heads up that Detekt 1.18.0 will be the last version to publish the detekt-bom artifact. Such artifact was used to align the dependency version used by detekt.
We now moved to use Gradle version catalog and we don't need detekt-bom anymore.
If you're depending on this artifact, please let us know your use case.
I'd publish it in the upcoming version say that this would potentially be the last release of the
detekt-bomartifact. This would allow us to understand if there are strong concerns or users depending heavily on it.Originally posted by @cortinico in #3688 (comment)
Just a heads up that Detekt
1.18.0will be the last version to publish thedetekt-bomartifact. Such artifact was used to align the dependency version used by detekt.We now moved to use Gradle version catalog and we don't need detekt-bom anymore.
If you're depending on this artifact, please let us know your use case.