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

[dependabot]

Bumps the bazel-packages group with 2 updates: 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.

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.

Baseline: b29e7f9d7f4016e668647e5c2f27a1dc1e0b5243

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

Release notes

Sourced from rules_cc's releases.

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")
http_archive(
name = "rules_cc",
sha256 = "69e05df29f0010ba248ef8dafc1f084c8fd2f5c553da634422d8167f5c4b277b",
strip_prefix = "rules_cc-0.2.20",
url = "https://github.com/bazelbuild/rules_cc/releases/download/0.2.20/rules_cc-0.2.20.tar.gz",
)
load("@​rules_cc//cc:extensions.bzl", "compatibility_proxy_repo")
compatibility_proxy_repo()

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

0.2.19

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

Using WORKSPACE:

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

... (truncated)

Commits

• 1abb3af Update rules_cc bazel_features dependency to version 1.50.0.
• a0d30c6 Add llvm-profdata action, support env
• 8d64d25 Reorganize rules_cc buildkite config.
• 8169167 Move remaining builtins_bzl test files to rules_cc.
• 5758824 Migrate C++ PDB and Coverage Support tests (Batch 3) to Starlark.
• 634f2e3 Add integration tests for Propeller linking. Also a small fix to propeller fe...
• 7eb96e3 Add env var to disable macOS toolchain
• f65555c Refactor cc_binary tests to use derived assertions instead of detached assert...
• 2796ad9 Make link_action_subject inputs/outputs return File objects.
• ab9f0cf Migrate several cc_binary tests from Java to Starlark.
• 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

[datadog-datadog-prod-us1]

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 6 Pipeline jobs failed

Development | build-windows-cmake (amd64)     

Development | build-linux-cmake (gnu, arm64)     

Development | build-linux-cmake (gnu, x64)     

View all 6 failed jobs.

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 9529171 | Docs | Datadog PR Page | Give us feedback!}

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-07-01 19:32:25

Comparing candidate commit 9529171 in PR branch dependabot/bazel/bazel-packages-9e06492fea with baseline commit d7ea3a8 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 👍 / 👎.