Add support for RAPIDS release process #548
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jameslamb
approved these changes
Apr 25, 2025
Member
jameslamb
left a comment
jameslamb
left a comment
There was a problem hiding this comment.
This looks great to me, I think you got all of the places that need to be updated. Thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds support for the RAPIDS release process to the deployment repository.
Changes:
ci/release/update-version.shscript to handle version updatessource/conf.pyconf.pyandREADME.mdManual steps:
branch-25.04branch to establish version reference for the burndown script.And:
build-and-deploy.ymlworkflowThis ensures that the deployment repository can be properly versioned and released as part of the regular RAPIDS release cycle.