build(deps): bump the bazel-packages group across 1 directory with 2 updates

[dependabot]

Bumps the bazel-packages group with 2 updates in the / directory: abseil-cpp and rules_cc.

Updates abseil-cpp from 20260107.1 to 20260526.0

Release notes

Sourced from abseil-cpp's releases.

Abseil LTS branch, May 2026

Abseil LTS 20260526.0

What's New

• status_macros.h: Helper macros and methods to return and propagate errors with absl::Status.
• absl::StatusBuilder: A builder type that implicitly converts to absl::Status and absl::StatusOr<T> that helps add additional information.
• absl::SourceLocation: A type that provides source-code location info for C++17 and later. It differs from std::source_location in several ways. See source_location.h for more information.
• absl::ClockInterface: An abstract interface representing a clock, allowing decoupling code that uses time from the code that creates a point in time. Useful for injecting clocks into interfaces, especially for testing purposes.
• absl::SimulatedClock: A concrete clock implementation that does not "tick" on its own. Useful for manipulating time for testing purposes.
• absl::AnySpan: A type that provides a view of any random access container.
• absl::optional_ref: A type that provides a std::optional-like interface around T*.
• absl::bind_back: A drop-in replacement for C++23's std::bind_back().
• absl::CopyCordToSpan: A safer way to copy the contents of an absl::Cord to a buffer.
• absl::HighPrecision: An absl::StrCat formatter that produces strings that would parse to the exact original floating point value (except in the case of NaNs).
• throw_delegate.h: Helper functions that allow throwing exceptions consistently from anywhere without risking ODR violations.

Breaking Changes

• For GCC users, Abseil now requires at least GCC 10 following Google's Foundational C++ Support Policy. See this table for a list of currently supported versions compilers, platforms, and build tools.
• Many pre-C++17 polyfill types are marked deprecated. Users should migrate to the std:: equivalent.

Known Issues

• Bazel's compatibility_level was deprecated in 8.6.0 and 9.1.0 and thus removed from MODULE.bazel. However, this is causing builds with Bazel versions prior to 8.6.0 and 9.1.0 to fail. The recommended workaround is to update to a newer version of Bazel.
• Abseil fails to compile with GCC 16 when BMI2 extensions are enabled. See #2071 for details.

Baseline: b29e7f9d7f4016e668647e5c2f27a1dc1e0b5243 Cherry-pick: 5650e9cf76d3be4318d5fa3af38ee483ddfd5e4a

Abseil LTS branch, May 2026, Release Candidate 1

Abseil LTS 20260526.rc1

What's New

• status_macros.h: Helper macros and methods to return and propagate errors with absl::Status.
• absl::StatusBuilder: A builder type that implicitly converts to absl::Status and absl::StatusOr<T> that helps add additional information.
• absl::SourceLocation: A type that provides source-code location info for C++17 and later. It differs from std::source_location in several ways. See source_location.h for more information.
• absl::ClockInterface: An abstract interface representing a clock, allowing decoupling code that uses time from the code that creates a point in time. Useful for injecting clocks into interfaces, especially for testing purposes.
• absl::SimulatedClock: A concrete clock implementation that does not "tick" on its own. Useful for manipulating time for testing purposes.
• absl::AnySpan: A type that provides a view of any random access container.
• absl::optional_ref: A type that provides a std::optional-like interface around T*.
• absl::bind_back: A drop-in replacement for C++23's std::bind_back().
• absl::CopyCordToSpan: A safer way to copy the contents of an absl::Cord to a buffer.
• absl::HighPrecision: An absl::StrCat formatter that produces strings that would parse to the exact original floating point value (except in the case of NaNs).
• throw_delegate.h: Helper functions that allow throwing exceptions consistently from anywhere without risking ODR violations.

Breaking Changes

• For GCC users, Abseil now requires at least GCC 10 following Google's Foundational C++ Support Policy. See this table for a list of currently supported versions compilers, platforms, and build tools.

... (truncated)

Commits

• 5650e9c Remove an obsolete //visibility:private tag (#2070)
• b29e7f9 Apply LTS transformations for 20260526 LTS branch (#2063)
• 147d631 Use absl::StripLeadingAsciiWhitespace instead of a lambda using std::isspace
• 635c53f Add extra tests for working with reserved tables.
• 54615fe Refactor ClearBackingArray and add test for clearing with different sizes.
• e9f87bc Disable inlining for some templated symbols in Abseil
• eb0e0d4 Add parentheses-removal support for non-VA_OPT-supporting compilers to st...
• f883d40 Fix comment in variant.h to refer to absl::variant.
• 0e9e3da Add an overload of absl::c_move to move between containers.
• b368f2c PR #2057: doc: clarify moved-from state for hash containers
• Additional commits viewable in compare view

Updates rules_cc from 0.2.14 to 0.2.21

Release notes

Sourced from rules_cc's releases.

0.2.21

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.21")

Using WORKSPACE:

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

Full Changelog: bazelbuild/rules_cc@0.2.20...0.2.21

0.2.20

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.20")

Using WORKSPACE:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
</tr></table>

... (truncated)

Commits

• 1a20833 Change default needs_include_validation to match createCppCompileAction's par...
• fad3ad3 Starlarkify compute_output_name_prefix_dir
• 593d6fc Remove unused variable
• 084155d Automatic code cleanup.
• da170e4 Revert toolchain expansions and introduce profile changelist defines to links...
• 5eeedeb Support the new(ish) @//tools/cpp:cc_runtimes_toolchain_type toolchain for ...
• 97e2922 Add Windows ThinLTO arguments
• beab926 Remove --incompatible_make_thinlto_command_lines_standalone from `test_lto_...
• f2e4ad2 Make default OSX toolchain respect the use_libtool flag
• a7a6249 Migrate batch 3 of CcBinaryThinLtoTest to Starlark
• Additional commits viewable in compare view

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-07-06 17:33:13

Comparing candidate commit 07cb90f in PR branch dependabot/bazel/bazel-packages-9e06492fea with baseline commit 6c29908 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 ----------------------------------'

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9529171f68

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Avoid requiring an unpinned Bazel upgrade

In builds that run Bzlmod with Bazel <8.6.0 (or pre-9.1.0 on the 9.x line), Abseil 20260526.0 is a known-bad release because its upstream MODULE.bazel removed compatibility_level; Abseil's release notes say those Bazel versions fail and recommend upgrading Bazel. This repo does not pin Bazel, and the Bazel job in .github/workflows/dev.yml invokes bazelisk --bazelrc=... build dd_trace_cpp, so users or CI images that have not moved to Bazel 8.6+/9.1+ can hit module-resolution failures before compilation; either pin/require a compatible Bazel version with this bump or stay on the previous Abseil LTS.

Useful? React with 👍 / 👎.