trunk check --show-existing Treating New Lint Violations as Existing Issues (v1.22.9)

[vtsachev]

A user has reported an issue where trunk check --show-existing appears to treat new lint violations as existing issues in version 1.22.9. Below is a summary of the observed behavior:

Reported Behavior

1. A file is modified in a branch to introduce a lint rule violation (e.g., Missing trailing comma before ")" with detekt-gradle).
2. Running ./trunk check --all correctly detects the new issue and exits with an error.

21:31 medium Missing trailing comma before ")" detekt-gradle/detekt.formatting.TrailingCommaOnDeclarationSite
✖ 1 lint issue

3. Running ./trunk check --show-existing on the modified files still detects the violation but classifies it as an existing issue instead of a new one.

21:31 medium Missing trailing comma before ")" detekt-gradle/detekt.formatting.TrailingCommaOnDeclarationSite
✔ No new issues

4. The issue persists even after running ./trunk logout and ./trunk cache clean.
5. The same behavior is observed whether the change is staged (git add) but not committed, or when included in a commit.

This behavior is impacting CI runs where trunk check is expected to fail on new issues but is instead passing.