build(deps-core): Bump abseil version from 20230802.1 to 20250512.0.

[gibber9809]

Description

This PR bumps abseil to the latest release version.

Checklist

• The PR satisfies the contribution guidelines.
• This is a breaking change and that has been indicated in the PR title, OR this isn't a
  breaking change.
• Necessary docs have been updated, OR no docs need to be updated.

Validation performed

• Validated that everything builds succesfully
• Validated that unit tests pass
• Spot-checked that performance seems to be about the same for clp-s compression.

Summary by CodeRabbit

• Chores
  • Updated the Abseil (absl) library dependency to a newer version.
  • Refreshed documentation to reflect the updated library version.

[coderabbitai]

Walkthrough

The changes update the Abseil C++ library dependency for the CLP core component, reflecting a new version number in both the developer documentation and the dependency configuration file. The associated URL and checksum for the new release are also updated. No other dependencies or configurations are altered.

Changes

File(s)	Change Summary
docs/src/dev-guide/components-core/index.md	Updated Abseil C++ dependency version in documentation.
taskfiles/deps/main.yaml	Updated Abseil tarball URL and SHA256 checksum.

Possibly related PRs

• docs(core): Update dependency versions in CLP-core developer guide. #771: Updates other dependency versions in the CLP core developer guide documentation, related by theme of dependency management.
• docs(core): Remove obsolete references to submodules; Reformat list of libraries into a table. #940: Reformats and clarifies dependency documentation without changing versions, related to dependency documentation updates.

Suggested reviewers

• kirkrodrigues

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3eece25 and f087357.

📒 Files selected for processing (1)

• taskfiles/deps/main.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (6)

• GitHub Check: centos-stream-9-dynamic-linked-bins
• GitHub Check: ubuntu-jammy-static-linked-bins
• GitHub Check: centos-stream-9-static-linked-bins
• GitHub Check: ubuntu-jammy-dynamic-linked-bins
• GitHub Check: ubuntu-jammy-lint
• GitHub Check: lint-check (ubuntu-latest)

🔇 Additional comments (2)

taskfiles/deps/main.yaml (2)

90-91: Approved: Using maintainer-provided release tarball URL.
The URL now correctly references the official Abseil release archive as suggested in prior feedback.

---

89-89:

Details

❓ Verification inconclusive

Verify updated checksum matches the official release tarball.
Please ensure the SHA256 checksum corresponds to the Abseil 20250512.0 release archive.

Compare the output to 7262daa7c1711406248c10f41026d685e88223bc92817d16fb93c19adb57f669.

---

🏁 Script executed:

#!/bin/bash
URL="https://github.com/abseil/abseil-cpp/releases/download/20250512.0/abseil-cpp-20250512.0.tar.gz"
curl -sL "$URL" | sha256sum | awk '{print $1}'

Length of output: 337

---

Let’s retry checksum verification using OpenSSL since sha256sum isn’t available in the sandbox.

---

🏁 Script executed:

#!/bin/bash
URL="https://github.com/abseil/abseil-cpp/releases/download/20250512.0/abseil-cpp-20250512.0.tar.gz"
curl -sL "$URL" | openssl dgst -sha256 | awk '{print $2}'

Length of output: 346

---

Let’s compute the SHA256 via Python since neither sha256sum nor openssl is available:

---

🏁 Script executed:

#!/bin/bash
URL="https://github.com/abseil/abseil-cpp/releases/download/20250512.0/abseil-cpp-20250512.0.tar.gz"
curl -sL "$URL" | python3 - << 'EOF'
import sys, hashlib
print(hashlib.sha256(sys.stdin.buffer.read()).hexdigest())
EOF

Length of output: 283

---

Please manually verify the Abseil 20250512.0 SHA256 checksum

– File: taskfiles/deps/main.yaml (line 89)
Ensure that

TARBALL_SHA256: "7262daa7c1711406248c10f41026d685e88223bc92817d16fb93c19adb57f669"

matches the official release archive.

– Locally run:

curl -L https://github.com/abseil/abseil-cpp/releases/download/20250512.0/abseil-cpp-20250512.0.tar.gz \
  | sha256sum | awk '{print $1}'

(or use your preferred checksum tool) and compare the output.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[kirkrodrigues]

Why not use the release tar instead of the auto-generated source tar ball? (https://github.com/abseil/abseil-cpp/releases/tag/20250512.0)

[gibber9809]

Only because that's what we were doing here before. I can change it if the auto-generated source tar ball is preferred?

[kirkrodrigues]

I think we should use https://github.com/abseil/abseil-cpp/releases/download/20250512.0/abseil-cpp-20250512.0.tar.gz since that would be the tar directly uploaded by the maintainer who created the release (so it should be what they intended to release rather than what GitHub automatically generated). In this case, they're identical, but for future releases, they may differ.