Update dependency rules_cc to v0.1.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
rules_cc	bazel_dep	minor	0.0.9 -> 0.1.0

---

Configuration

📅 Schedule: 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.

[codiumai-pr-agent-pro]

CI Failure Feedback 🧐

(Checks updated until commit e9da39c)

Action: Format / Check format script run

Failed stage: Run Bazel [❌]

Failed test name: ""

Failure summary: The action failed due to multiple issues in the build process: There are duplicate artifact versions found in the Maven repository, which can lead to unexpected artifact versions: - com.google.code.gson:gson has versions 2.11.0 and 2.8.9. - com.google.guava:guava has versions 33.3.1-jre and 31.1-jre. - org.mockito:mockito-core has versions 5.14.2 and 4.3.1. A critical error occurred because the file @rules_cc//cc:defs.bzl does not contain the symbol cc_proto_library. There is a missing target GenClass in the package defined by /home/runner/.bazel/external/rules_java~~toolchains~remote_java_tools/BUILD. The analysis of the target //scripts:google-java-format failed, causing the build to abort.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 970: Package 'php-symfony-debug-bundle' is not installed, so not removed 971: Package 'php-symfony-dependency-injection' is not installed, so not removed 972: Package 'php-symfony-deprecation-contracts' is not installed, so not removed 973: Package 'php-symfony-discord-notifier' is not installed, so not removed 974: Package 'php-symfony-doctrine-bridge' is not installed, so not removed 975: Package 'php-symfony-doctrine-messenger' is not installed, so not removed 976: Package 'php-symfony-dom-crawler' is not installed, so not removed 977: Package 'php-symfony-dotenv' is not installed, so not removed 978: Package 'php-symfony-error-handler' is not installed, so not removed ... 1757: �[33mDEBUG: �[0m/home/runner/.bazel/external/rules_jvm_external~/private/extensions/maven.bzl:152:14: The maven repository 'maven' is used in two different bazel modules, originally in 'selenium' and now in 'protobuf' 1758: �[33mDEBUG: �[0m/home/runner/.bazel/external/rules_jvm_external~/private/extensions/maven.bzl:152:14: The maven repository 'maven' is used in two different bazel modules, originally in 'selenium' and now in 'protobuf' 1759: �[33mDEBUG: �[0m/home/runner/.bazel/external/rules_jvm_external~/private/extensions/maven.bzl:152:14: The maven repository 'maven' is used in two different bazel modules, originally in 'selenium' and now in 'protobuf' 1760: �[33mDEBUG: �[0m/home/runner/.bazel/external/rules_jvm_external~/coursier.bzl:754:18: Found duplicate artifact versions 1761: com.google.code.gson:gson has multiple versions 2.11.0, 2.8.9 1762: com.google.guava:guava has multiple versions 33.3.1-jre, 31.1-jre 1763: org.mockito:mockito-core has multiple versions 5.14.2, 4.3.1 1764: Please remove duplicate artifacts from the artifact list so you do not get unexpected artifact versions 1765: �[31m�[1mERROR: �[0mTraceback (most recent call last): 1766: File "/home/runner/.bazel/external/rules_java~~toolchains~remote_java_tools/BUILD", line 7, column 60, in <toplevel> 1767: load("@rules_cc//cc:defs.bzl", "cc_binary", "cc_library", "cc_proto_library") 1768: Error: file '@rules_cc//cc:defs.bzl' does not contain symbol 'cc_proto_library' 1769: �[31m�[1mERROR: �[0m/home/runner/.bazel/external/rules_java~~toolchains~remote_java_tools/BUILD: no such target '@@rules_java~~toolchains~remote_java_tools//:GenClass': target 'GenClass' not declared in package '' defined by /home/runner/.bazel/external/rules_java~~toolchains~remote_java_tools/BUILD 1770: �[31m�[1mERROR: �[0m/home/runner/.bazel/external/rules_java~/toolchains/BUILD:305:27: no such target '@@rules_java~~toolchains~remote_java_tools//:GenClass': target 'GenClass' not declared in package '' defined by /home/runner/.bazel/external/rules_java~~toolchains~remote_java_tools/BUILD and referenced by '@@rules_java~//toolchains:toolchain_jdk_17' 1771: �[31m�[1mERROR: �[0mAnalysis of target '//scripts:google-java-format' failed; build aborted: Analysis failed 1772: �[32mINFO: �[0mElapsed time: 25.958s, Critical Path: 0.05s 1773: �[32mINFO: �[0m1 process: 1 internal. 1774: �[31m�[1mERROR: �[0mBuild did NOT complete successfully 1775: �[31m�[1mFAILED:�[0m 1776: �[31m�[1mERROR: �[0mBuild failed. Not running target 1777: �[0m 1778: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.