Skip to content

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

Merged
nvauto merged 1 commit intorelease/26.04from
bot-submodule-sync-release/26.04
Mar 19, 2026
Merged

[submodule-sync] bot-submodule-sync-release/26.04 to release/26.04 [skip ci] [bot]#4399
nvauto merged 1 commit intorelease/26.04from
bot-submodule-sync-release/26.04

Conversation

@nvauto
Copy link
Copy Markdown
Collaborator

@nvauto nvauto commented Mar 19, 2026

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

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

Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
@nvauto
Copy link
Copy Markdown
Collaborator Author

nvauto commented Mar 19, 2026

HEAD commit SHA: 04eaec8, CUDF commit SHA: rapidsai/cudf@a9064fe
Test passed: True

@nvauto nvauto merged commit bf88119 into release/26.04 Mar 19, 2026
@nvauto
Copy link
Copy Markdown
Collaborator Author

nvauto commented Mar 19, 2026

SUCCESS - auto-merge

@nvauto nvauto deleted the bot-submodule-sync-release/26.04 branch March 19, 2026 03:59
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 19, 2026

Greptile Summary

This is an automated bot PR that advances the thirdparty/cudf git submodule pointer from commit b13ada2 to a9064fe on the release/26.04 branch, keeping the vendored cuDF dependency in sync with its upstream rapidsai/cudf repository.

  • Only change is the submodule commit SHA recorded in .gitmodules/thirdparty/cudf
  • No source code, build scripts, or configuration files in this repository were modified
  • The PR is auto-generated by the nvauto bot and is configured to auto-merge once CI passes
  • No issues found — this is a routine dependency bump

Confidence Score: 5/5

  • This PR is safe to merge — it is a single-file submodule pointer bump generated by the nvauto automation bot.
  • The only change is advancing the thirdparty/cudf submodule SHA. No first-party source code, build configuration, or tests were modified. The PR is part of an established automated sync workflow and is designed to auto-merge once CI validates compatibility.
  • No files require special attention.

Important Files Changed

Filename Overview
thirdparty/cudf Submodule pointer updated from b13ada2c8970be62e713d197e0ad3fa596ea32ef to a9064fedc61880eae66c88000b93a97b1cc2ed92 (rapidsai/cudf) — automated bot sync with no code changes in this repository.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[nvauto bot detects cudf upstream changes] --> B[Creates PR: bot-submodule-sync-release/26.04]
    B --> C{CI passes?}
    C -- Yes --> D[Auto-merge into release/26.04]
    C -- No --> E[PR remains open for manual fix]
    D --> F[thirdparty/cudf pointer\nupdated: b13ada2 → a9064fe]
Loading

Last reviewed commit: "Update submodule cud..."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant