chore(deps): update dependency github/codeql-cli-binaries to v2.26.4 - autoclosed

[renovate]

This PR contains the following updates:

Package	Update	Change
github/codeql-cli-binaries	patch	2.26.3 → 2.26.4

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

github/codeql-cli-binaries (github/codeql-cli-binaries)

v2.26.4

Compare Source

New Features

• codeql test run now supports the --reuse-dataset option, which
  reuses an existing test database from a previous run when available,
  skipping database extraction. This can speed up repeated test runs
  when only the query under test has changed. The option implies
  --keep-databases.

Bug Fixes

• The Java Autobuilder now expands project properties, such as
  ${maven.version}, when determining Maven version requirements specified
  by the Maven Enforcer Plugin. The Java Autobuilder now also supports Maven
  versions through 3.9.16.

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • At any time (no schedule defined)
• 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 was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[github-actions]

✅ Supply Chain Verification Results

✅ PASSED

📦 SBOM Summary

• Components: 1754

🔍 Vulnerability Scan

Severity	Count
🔴 Critical	0
🟠 High	0
🟡 Medium	5
🟢 Low	2
Total	11

📎 Artifacts

• SBOM (CycloneDX JSON) and Grype results available in workflow artifacts

---

_{Generated by Supply Chain Verification workflow • View Details}