Just to make sure that I have understood correctly...

# detekt

[strindberg]

Just to make sure that I have understood correctly: with the new release (2.0.0-alpha.6), is running "gradle detektMain" no longer necessary to catch more issues than what is already wired in (e.g. by running "gradle check") when detekt is active?

[Brais Gabin]

Where did you understand that? As far as I know nothing changed in this area yet.

[strindberg]

This, from the release notes, made me think that might be the case: "Notable Changes: The detekt Gradle task now analyzes all Kotlin source sets with type resolution by default, replacing the previous type-resolution-free task."

[Gama11]

I just tried that as well, and found that detektMain results in more findings than detekt

[Gama11]

PR #7025 linked in the release notes there also seems completely unrelated

[Gama11]

since it's from 2024 and wasn't even merged

[strindberg]

Thanks for checking this. I must have misunderstood.

[Gama11]

no no, I had exactly the same misunderstanding because of the release notes, that's why I opened slack to ask about it

[Gama11]

only to find out I'm not the first person who is confused 😄

[Gama11]

it almost feels like release notes were generated by an AI based on recently closed PRs or something... 😄

[strindberg]

😃

[Zsolt.bertalan]

Me too. But I still don't understand, why it is not relevant anymore.

[gammax]

Ooops that's my bad. My changelog generation script did not filter not-merged PRs. Let me follow-up on this.