Nelson Osacky

The Detekt project benefitted from a savings of 14min on average on CI from the local build cache in the last 7 days. [Here is the data](https://ge.detekt.dev/scans/trends?search.startTimeMax=1707300683783&search.startTimeMin=1706655600000&search.tags=ci&search.timeZoneId=Europe%2FBerlin&trends.activeMetrics=%7B%22avoidanceSavings%22:%22localBuildCache%22%7D&trends.section=avoidanceSavings)

Yes, you can declare a task not compatible with configuration cache: https://docs.gradle.org/current/userguide/configuration_cache.html#config_cache:task_opt_out

Released in 0.9.0

How do you suggest that these have been overridden accidentally?

Thanks for letting us know. Not having Intellij instructions is a separate issue than the one described in this ticket. Please file separately.

How can this be detected? I feel like this is a bit out of scope of the Gradle doctor though.

Here's a screenshot of the staging profiles in the web UI:  I wasn't sure what you mean by the name of the automatically created staging repositories. Is it just...

Yes, I usually do get 3 of them when publishing, but I cannot remember their names.

Any updates on here or any way I can help?

@BreadMoirai friendly reminder about this security vulnerability! :)