[submodule-sync] bot-submodule-sync-release/26.04 to release/26.04 [skip ci] [bot]

[nvauto]

submodule-sync to create a PR keeping thirdparty/cudf up-to-date.
HEAD commit SHA: a5ec020, cudf commit SHA: rapidsai/cudf@b13ada2

This PR will be auto-merged if test passed. If failed, it will remain open until test pass or manually fix.

[nvauto]

HEAD commit SHA: a5ec020, CUDF commit SHA: rapidsai/cudf@b13ada2
Test passed: True

[nvauto]

SUCCESS - auto-merge

[greptile-apps]

Greptile Summary

This is an automated submodule-sync PR generated by the nvauto bot to keep the thirdparty/cudf dependency up-to-date on the release/26.04 branch. The sole change is advancing the rmm package pin in thirdparty/cudf-pins/versions.json to commit b5c81cdc43d3ba04027b20cd8b839385313ac3e3 (from 6ed480503ea740a0eb2c3fdac0c0a4a88c778027), tracking the cudf HEAD at b13ada2c8970be62e713d197e0ad3fa596ea32ef.

• Only one field changed: packages.rmm.git_tag in thirdparty/cudf-pins/versions.json
• All other dependency pins (CCCL, GTest, cuco, kvikio, rapids_logger, etc.) are left untouched
• JSON structure is valid and well-formed
• No logic issues or security concerns identified; the PR is intended to auto-merge once CI passes

Confidence Score: 5/5

• This PR is safe to merge — it is a single-field, bot-generated dependency pin update with no logic or structural risk.
• The change is minimal and mechanical: one Git SHA updated in a version-pin JSON file, produced by an automated sync bot. The JSON remains valid and all other pinned dependencies are unmodified. Risk is entirely governed by whether the new rmm commit is stable, which is validated by CI.
• No files require special attention.

Important Files Changed

Filename	Overview
thirdparty/cudf-pins/versions.json	Automated bump of the rmm dependency git_tag from 6ed480503ea740a0eb2c3fdac0c0a4a88c778027 to b5c81cdc43d3ba04027b20cd8b839385313ac3e3; all other dependency pins are unchanged and the JSON remains well-formed.

Sequence Diagram

sequenceDiagram
    participant Bot as nvauto Bot
    participant cudf as rapidsai/cudf
    participant rmm as rapidsai/rmm
    participant repo as spark-rapids-jni
    participant CI as CI Pipeline

    cudf->>rmm: tracks new rmm commit (b5c81cdc...)
    Bot->>cudf: reads HEAD commit (b13ada2c...)
    Bot->>repo: opens PR updating versions.json rmm git_tag
    repo->>CI: runs tests against new rmm pin
    CI-->>repo: pass → auto-merge

Loading

_{Last reviewed commit: "Update pinned versio..."}