build(deps): bump rules_cc from 0.2.14 to 0.2.25 in the bazel-packages group

[dependabot]

Bumps the bazel-packages group with 1 update: rules_cc.

Updates rules_cc from 0.2.14 to 0.2.25

Release notes

Sourced from rules_cc's releases.

0.2.25

Using bzlmod with Bazel 6 or later:

1. [Bazel 6] Add common --enable_bzlmod to .bazelrc.

2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_cc", version = "0.2.25")

Using WORKSPACE:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
name = "rules_cc",
sha256 = "bd7124a844d0403b4b353bcea34d6c8b2ba88dc26881c26c9ee668da89b71846",
strip_prefix = "rules_cc-0.2.25",
url = "https://github.com/bazelbuild/rules_cc/releases/download/0.2.25/rules_cc-0.2.25.tar.gz",
)
load("@​rules_cc//cc:extensions.bzl", "compatibility_proxy_repo")
compatibility_proxy_repo()

What's Changed

Notable changes

• Throw an error if include attributes contain an absolute path instead of silently ignoring them. by @​a-googler in c85b4d3179cfb51a20a5380c26b7e28cf1a63609
• Disable macOS toolchain by default (use apple_support instead) by @​keith in 0c36f2bb6c2421e2416040d214641d7abe89b31b
• Allow 'includes = ["."]' in the root of the repo by @​keith in 0d150d5268c362c0da2cbb497d9c03d1466c2bee
• Add //cc/libc config settings for C standard libraries (#792) by @​fmeum in dc424059b634480fdca0250e4ecc2af88f127059
• Add best effort toolchain feature docs by @​keith in 2c276638d159b2bd97fd139a67d6c00cd92e2e91
• Add loongarch64 support by @​zhaixiaojuan in 51784080f788bc816242bf1362d76cf14f306107
• Support path mapping in CppLink IFF it's non-lto. by @​lilygorsheneva in ad214a9cb17d41e4e03199d61d436974a2261885
• Create features to enable/disable path mapping for CppLink. by @​lilygorsheneva in ab613e1060c895e45689aa79f951e5f1a6d3c193
• Add toolchain env + default env to dwp actions by @​keith in d8eea5a37fb096c879127e66c3f1845d9587db05
• Fix system_include_paths with textual_hdrs/hdrs and strip_include_prefix by @​keith in db798494c28debf440576d79dc97b254908dcfb0
• Expose Bazel cc rule functions for extension by @​hvadehra in 6c6a87ed23335eda4d01c12f4a10965897813d56
• Expand tree artifacts in textual_hdrs in generated module maps (#787) by @​fmeum in 6cc1bf04ed7a89e39788cea1e10738136c9dd082
• Honor object extensions for ThinLTO merged artifacts (#853) by @​cerisier in aff544134bc9d29006f27adbe63d824dfe1436f6
• Expose a new API that copying from an existing library with overrides, so that callers don't need to know all internal attributes to avoid silently dropping some. by @​a-googler in 14686ad81e1cd50c8d2bf2ae3e2d45eb16339943
• Implement Starlark-level enforcement of disallowed compiler flags in copts, conlyopts, cxxopts. by @​a-googler in f687cbc1bd9e23e1eeb61072ac8dc01d8577d793
• Move coverage script / flag to public package (#867) by @​keith in 661b75de668c3b673f5550e0340e134ccf923956
• Support C++20 modules, GCC part by @​PikachuHyA in faf2113fe24f2676afbe4fec7eaf0bbd15818698

... (truncated)

Commits

• 77064f0 Skip C++20 test if missing clang-scan-deps (#880)
• 661b75d Move coverage script / flag to public package (#867)
• 3000380 Default cc_sysroot data to sysroot if not passed (#875)
• c1ba7a0 Fix unused variable buildifier warning now that this always returns true.
• 5ef9b69 Remove MODULE.bazel.lock usage from integration tests (#866)
• fb4d05e No public description
• a7a2e15 Remove my ownership from most of rules_cc
• f687cbc Implement Starlark-level enforcement of disallowed compiler flags in copts, c...
• de72c61 Support C++20 modules, MSVC part (#836)
• 5e0038d Fix cc_integration_test workspace isolation and toolchain guards under Bzlmod.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-10-01 19:35:01

Comparing candidate commit 7b96fd3 in PR branch dependabot/bazel/bazel-packages-b51bee33d3 with baseline commit 7059aed in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 8 metrics, 0 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'