Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep rapids cmake version in sync #876

Conversation

robertmaynard
Copy link
Contributor

Make sure we keep the rapids-cmake and rmm cal version in sync

when we make a new rmm version, we need to also bump the rapids-cmake version at the same time. Otherwise we will get the previous releases dependencies by mistake.

when we make a new rmm version, we need to also bump the rapids-cmake version at the same time. Otherwise we will get the previous releases dependencies by mistake.
@robertmaynard robertmaynard added bug Something isn't working CMake non-breaking Non-breaking change labels Sep 20, 2021
@robertmaynard robertmaynard requested review from a team as code owners September 20, 2021 12:38
@github-actions github-actions bot added cpp Pertains to C++ code gpuCI Python Related to RMM Python API labels Sep 20, 2021
@robertmaynard robertmaynard changed the base branch from branch-21.10 to branch-21.12 September 20, 2021 12:39
@robertmaynard robertmaynard removed the request for review from a team September 20, 2021 12:40
@robertmaynard robertmaynard removed the Python Related to RMM Python API label Sep 20, 2021
@robertmaynard
Copy link
Contributor Author

rerun tests

@harrism
Copy link
Member

harrism commented Sep 21, 2021

@gpucibot merge

@rapids-bot rapids-bot bot merged commit b512690 into rapidsai:branch-21.12 Sep 21, 2021
@robertmaynard robertmaynard deleted the keep_rapids-cmake-version-in-sync branch September 21, 2021 12:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CMake cpp Pertains to C++ code gpuCI non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants