Skip to content

[auto-merge] bot-auto-merge-release/26.04 to main [skip ci] [bot]#4419

Merged
nvauto merged 1 commit intomainfrom
bot-auto-merge-release/26.04
Mar 31, 2026
Merged

[auto-merge] bot-auto-merge-release/26.04 to main [skip ci] [bot]#4419
nvauto merged 1 commit intomainfrom
bot-auto-merge-release/26.04

Conversation

@nvauto
Copy link
Copy Markdown
Collaborator

@nvauto nvauto commented Mar 31, 2026

auto-merge triggered by github actions on bot-auto-merge-release/26.04 to create a PR keeping main up-to-date. If this PR is unable to be merged due to conflicts, it will remain open until manually fix.

Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
@nvauto nvauto merged commit bb4c68a into main Mar 31, 2026
@nvauto
Copy link
Copy Markdown
Collaborator Author

nvauto commented Mar 31, 2026

SUCCESS - auto-merge

@nvauto nvauto deleted the bot-auto-merge-release/26.04 branch March 31, 2026 05:10
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 31, 2026

Greptile Summary

This is a routine automated merge from bot-auto-merge-release/26.04 into main, keeping the main branch up to date with the latest release cycle. No production code was modified — all four changed files are dependency pins and submodule pointers.

Key changes:

  • .gitmodules: The thirdparty/cudf submodule tracking branch is reset from release/26.04 back to main, which is the expected state after integrating a release into main.
  • thirdparty/cudf: The submodule pointer is advanced to a newer cudf commit (01c7ada) on the main branch.
  • thirdparty/cudf-pins/rapids-cmake.sha: rapids-cmake SHA updated to fa303cb88 to stay in sync with the cudf main pin.
  • thirdparty/cudf-pins/versions.json: kvikio and rmm versions jump from 26.0426.06 with updated git SHAs. This skip is expected — RAPIDS follows a bi-monthly release cadence (April → June), so 26.05 does not exist as a release.

No issues were identified; this PR is a safe, automated bookkeeping update.

Confidence Score: 5/5

Safe to merge — only submodule pointers and dependency version pins are updated, no source code changes.

All changes are automated dependency/submodule updates. No logic, API contracts, or build scripts were modified. The version jump from 26.04 to 26.06 is consistent with the RAPIDS bi-monthly release schedule and reflects upstream cudf main branch state. No P0/P1 findings.

No files require special attention.

Important Files Changed

Filename Overview
.gitmodules Submodule tracking branch for thirdparty/cudf updated from release/26.04 to main, consistent with merging a release branch back into main.
thirdparty/cudf cudf submodule pointer advanced to a newer commit on main (fb3682f → 01c7ada), aligned with the updated tracking branch.
thirdparty/cudf-pins/rapids-cmake.sha rapids-cmake SHA bumped to fa303cb88 to match the cudf main branch pin; routine dependency update.
thirdparty/cudf-pins/versions.json kvikio and rmm dependency versions bumped from 26.04 → 26.06 (RAPIDS bi-monthly cycle; 26.05 does not exist) with updated git_tag SHAs.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[bot-auto-merge-release/26.04] -->|auto-merge| B[main]
    B --> C{Files Updated}
    C --> D[.gitmodules\nbranch: release/26.04 → main]
    C --> E[thirdparty/cudf\nfb3682f → 01c7ada]
    C --> F[rapids-cmake.sha\n9753c6b → fa303cb]
    C --> G[versions.json\nkvikio 26.04 → 26.06\nrmm 26.04 → 26.06]
Loading

Reviews (1): Last reviewed commit: "Auto-merge use main versions" | Re-trigger Greptile

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