Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions MODULE.bazel
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ module(
version = "2.0.1",
)

bazel_dep(name = "abseil-cpp", version = "20260107.1", repo_name = "com_google_absl")
bazel_dep(name = "abseil-cpp", version = "20260526.0", repo_name = "com_google_absl")

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

bazel_dep(name = "bazel_skylib", version = "1.9.0")
bazel_dep(name = "platforms", version = "1.1.0")
bazel_dep(name = "rules_cc", version = "0.2.18")
bazel_dep(name = "rules_cc", version = "0.2.20")
Loading