refactored update-version.sh to handle new branching strategy#323
Merged
rapids-bot[bot] merged 3 commits intorapidsai:mainfrom Nov 13, 2025
Conversation
Contributor
Author
|
command ❯ ./ci/release/update-version.sh --run-context=main 26.02.00
Using run-context from CLI: main
Preparing development branch update for 26.02.00 (targeting main branch)
Updating to 26.02.001 file changes ❯ git status
On branch ops-4339-update-version-sh-support-main-branching-strategy
Your branch is up to date with 'origin/ops-4339-update-version-sh-support-main-branching-strategy'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: VERSIONfull diff ❯ git diff | cat
diff --git a/VERSION b/VERSION
index 7924af6..5c33046 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-25.12.00
+26.02.00 |
Contributor
Author
|
command ❯ ./ci/release/update-version.sh --run-context=release 25.12.00
Using run-context from CLI: release
Preparing release branch update for 25.12.00 (targeting release/25.12 branch)
Updating to 25.12.000 files changed ❯ git status
On branch ops-4339-update-version-sh-support-main-branching-strategy
Your branch is up to date with 'origin/ops-4339-update-version-sh-support-main-branching-strategy'.
nothing to commit, working tree cleanfull diff ❯ git diff | cat |
rockhowse
added
bug
AyodeAwe
approved these changes
Nov 13, 2025
bdice
approved these changes
Nov 13, 2025
Contributor
Author
|
Not looking optimistic on that OpenSSL bump... anything that takes over 15 min here will most likely timeout at the 45 min mark. |
Contributor
Ugh, why couldn't it timeout on the initial PR... |
Contributor
|
PR reverting the |
Contributor
Author
|
/merge |
Closed
Merged
rapids-bot bot
pushed a commit
that referenced
this pull request
Jan 16, 2026
I just merged #347 into `release/26.02` and after a few minutes hadn't seen it forward-merged to `main`. Looks like automatic forward mergers are not set up here. They should be, now that we're producing RAPIDS-versioned images (rapidsai/build-planning#187) and using the new RAPIDS branching strategy (#323). This enables forward mergers. This also `git cherry-pick`s over the changes from #347 so they'll make it onto `main`. Authors: - James Lamb (https://github.com/jameslamb) Approvers: - Bradley Dice (https://github.com/bdice) - Nate Rock (https://github.com/rockhowse) URL: #350
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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 supports handling the new main branch strategy outlined below:
The
update-version.shscript should now supports two modes controlled viaCLIparams orENVvars:CLI arguments:
--run-context=main|releaseENV var
RAPIDS_RUN_CONTEXT=main|releasexref: rapidsai/build-planning#224