Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, pmd/pmd-github-action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

This rule reports suppression comments and annotations that did not suppress any PMD violation. Note that violations of this rule cannot be suppressed. Please note: - The rule will report those suppressions comments/annotations that did not suppress a violation _during the current run_. That means you cannot run this rule separately from other rules, it must always be run with all the rules that could produce a warning. This is most likely not a problem, as you can just include this rule in your regular ruleset. - The rule for now only reports annotations specific to PMD, like `@SuppressWarnings("PMD")`. For instance `@SuppressWarnings("all")` is never reported as we cannot know if another tool is producing a warning there that must be suppressed. In the future we might be able to check for other common ones like `@SuppressWarnings("unchecked")` or `"fallthrough"`. UnnecessaryWarningSuppression (Priority: 3, Ruleset: Best Practices) https://docs.pmd-code.org/snapshot/pmd_rules_java_bestpractices.html#unnecessarywarningsuppression

This rule reports suppression comments and annotations that did not suppress any PMD violation. Note that violations of this rule cannot be suppressed. Please note: - The rule will report those suppressions comments/annotations that did not suppress a violation _during the current run_. That means you cannot run this rule separately from other rules, it must always be run with all the rules that could produce a warning. This is most likely not a problem, as you can just include this rule in your regular ruleset. - The rule for now only reports annotations specific to PMD, like `@SuppressWarnings("PMD")`. For instance `@SuppressWarnings("all")` is never reported as we cannot know if another tool is producing a warning there that must be suppressed. In the future we might be able to check for other common ones like `@SuppressWarnings("unchecked")` or `"fallthrough"`. UnnecessaryWarningSuppression (Priority: 3, Ruleset: Best Practices) https://docs.pmd-code.org/snapshot/pmd_rules_java_bestpractices.html#unnecessarywarningsuppression

Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.