Hi, recently we have seen in our Jenkins CI that previous errors shows up as "new" in warnings NG plugin even when only the line number changes.

What fields are important for warnings NG to understand/detect if it's new or not? Has anything changes in the algorithm recently?

Some lint tools seems to more severely affected by this (could just be the amount of errors are more which makes it more difficult for warnings-NG). What part of the output does warnings-NG care about?

For example, ruff lint outputs a json format that is then rearranged for warnings-ng to understand.

Pylint creates a textfile that is parsed using `recordIssues(..., tool: pyLint("pylint.report"))` - can I run this manually on the commandline somehow? (outside of a Jenkins machine?)

https://github.com/jenkinsci/warnings-ng-plugin/blob/main/doc/Documentation.md#issues-history-new-fixed-and-outstanding-issues