chore(deps): update dependency com.github.spotbugs:spotbugs-annotations to v4.9.0

[solrbot]

This PR contains the following updates:

Package	Type	Update	Change
com.github.spotbugs:spotbugs-annotations (source)	dependencies	minor	4.8.6 -> 4.9.0

---

Release Notes

spotbugs/spotbugs (com.github.spotbugs:spotbugs-annotations)

v4.9.0

Compare Source

Added

• Updated the SuppressFBWarnings annotation to support finer grained bug suppressions (#​3102)
• SimpleDateFormat, DateTimeFormatter, FastDateFormat string check for bad combinations of flag formatting (#​637)
• New detector ResourceInMultipleThreadsDetector and introduced new bug type:
  • AT_UNSAFE_RESOURCE_ACCESS_IN_THREAD is reported in case of unsafe resource access in multiple threads.

Fixed

• Do not consider Records as Singletons (#​2981)
• Keep a maximum of 10000 cached analysis entries for plugin's analysis engines (#​3025)
• Only report MC_OVERRIDABLE_METHOD_CALL_IN_READ_OBJECT when calling own methods (#​2957)
• Check the actual caught exceptions (instead of their common type) when analyzing multi-catch blocks (#​2968)
• System property findbugs.refcomp.reportAll is now being used. For some new conditions, it will emit an experimental warning (#​2988)
• -version flag prints the version to the standard output (#​2797)
• Revert the changes from (#​2894) to get HTML stylesheets to work again (#​2969)
• Fix FP SING_SINGLETON_GETTER_NOT_SYNCHRONIZED report when the synchronization is in a called method (#​3045)
• Let BetterCFGBuilder2.isPEI handle dup2 bytecode used by Spring AOT (#​3059)
• Detect failure to close RocksDB's ReadOptions (#​3069)
• Fix FP EI_EXPOSE_REP when there are multiple immutable assignments (#​3023)
• Fixed false positive NP_NONNULL_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR for Kotlin, handle Kotlin's Intrinsics.checkNotNullParameter() (#​3094)
• Fixed some CWE mappings (#​3124)
• Recognize some classes as immutable, fixing EI_EXPOSE and MS_EXPOSE FPs (#​3137)
• Do not report UWF_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR for fields initialized in method annotated with TestNG's @​BeforeClass. (#​3152)
• Fixed detector FindReturnRef not finding references exposed from nested and inner classes (#​2042)
• Fix call graph, include non-parametric void methods (#​3160)
• Fix multiple reporting of identical bugs messing up statistics (#​3185)
• Added missing comma between line number and confidence when describing matching and mismatching bugs for tests (#​3187)
• Fixed method matchers with array types (#​3203)
• Fix SARIF report's message property in Exception to meet the standard (#​3197)
• Fixed FI_FINALIZER_NULLS_FIELDS FPs for functions called finalize() but not with the correct signature. (#​3207)
• Fixed an error in the detection of bridge methods causing analysis crashes (#​3208)
• Fixed detector ThrowingExceptions by removing false positive reports, such as synthetic methods (lambdas), methods which inherited their exception specifications and methods which call throwing methods (#​2040)
• Do not report DP_DO_INSIDE_DO_PRIVILEGED, DP_CREATE_CLASSLOADER_INSIDE_DO_PRIVILEGED and USC_POTENTIAL_SECURITY_CHECK_BASED_ON_UNTRUSTED_SOURCE in code targeting Java 17 and above, since it advises the usage of deprecated method (#​1515).
• Fixed a RV_RETURN_VALUE_IGNORED_NO_SIDE_EFFECT false positive for a builder delegating to another builder (#​3235)

Cleanup

• Cleanup thread issue and regex issue in test-harness (#​3130)
• Remove extra blank lines and remove public from interface objects as inherently already public (#​3131)
• Fix order of modifiers on properties/methods and ensure correct location in file (#​3132, #​3177)
• Return objects directly instead of creating more garbage collection by defining them (#​3133, #​3175)
• Restrict the constructor of abstract classes visibility to protected (#​3178)
• Cleanup double initialization and fix comments referring to findbugs instead of spotbugs(#​3134)
• Use diamond operator in constructor calls of Collections (#​3176)
• Use Collection.isEmpty() or String.isEmpty() to test for emptiness (#​3180, #​3219)
• Use method references instead of lambdas where possible (#​3179)
• Move default clauses to the end of switches (#​3222)
• Remove unnecessary throws declarations (#​3220)
• Use Boolean.parseBoolean() for string-to-boolean conversion. (#​3217)
• Rename shadowing fields (#​3221)
• Combine catch blocks with the same body (#​3223)
• Merge conditions of nested ifs (#​3231)
• Use non deprecated 'getDottedClassName' instead of 'toDottedClassName'(#​3251)
• Use try with resources where possible (#​3253)

Changed

• Bump up Java version to 11

---

Configuration

📅 Schedule: Branch creation - "* * * * *" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot

[solrbot]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: gradle/libs.versions.toml

Command failed: ./gradlew --console=plain --dependency-verification lenient -q :dependencies :solr:dependencies :solr:api:dependencies :solr:benchmark:dependencies :solr:core:dependencies :solr:cross-dc-manager:dependencies :solr:distribution:dependencies :solr:docker:dependencies :solr:documentation:dependencies :solr:example:dependencies :solr:modules:dependencies :solr:packaging:dependencies :solr:prometheus-exporter:dependencies :solr:server:dependencies :solr:solr-ref-guide:dependencies :solr:solrj:dependencies :solr:solrj-streaming:dependencies :solr:solrj-zookeeper:dependencies :solr:test-framework:dependencies :solr:webapp:dependencies :solr:modules:analysis-extras:dependencies :solr:modules:clustering:dependencies :solr:modules:cross-dc:dependencies :solr:modules:extraction:dependencies :solr:modules:gcs-repository:dependencies :solr:modules:hdfs:dependencies :solr:modules:jwt-auth:dependencies :solr:modules:langid:dependencies :solr:modules:llm:dependencies :solr:modules:ltr:dependencies :solr:modules:opentelemetry:dependencies :solr:modules:s3-repository:dependencies :solr:modules:scripting:dependencies :solr:modules:sql:dependencies --update-locks com.github.spotbugs:spotbugs-annotations

FAILURE: Build failed with an exception.

* What went wrong:
Failed to notify task execution graph listener.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.
> Use the ':writeLocks' task to write the lock file, '--write-locks' along is not sufficient.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.

BUILD FAILED in 15s