[REVIEW] Fix branch version in CI scripts

[galipremsagar]

Description

This PR fixes missed version upgrades in scripts.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[bdice]

Is this automated correctly? It looks like line 104 of update-version.sh should've fixed this. Here's raft's code, for comparison:

https://github.com/rapidsai/raft/blob/22ebc72e8c0c2738a30a0bbf9b0efc52736eddd6/ci/release/update-version.sh#L64-L67

[galipremsagar]

It is automated correctly in cudf:

https://github.com/rapidsai/cudf/blob/branch-23.04/ci/release/update-version.sh#L101

I verified running it locally and the script did the job locally and should've upgraded this automatically in CI too but looks like somehow it didn't change this value.

[raydouglass]

Looks like this is a BSD sed vs GNU sed issue. When I run this script during burndown, I use my Mac which uses BSD sed and it misses this change. When I updated to gsed in the update-version.sh script it worked as expected.

Let me think about how to handle this in the future.

[galipremsagar]

Thanks @raydouglass 🙏

[ajschmidt8]

I assume (though cannot confirm since I don't use a Mac) that the issue with that expression lies within this string: branch-[^\"\s]\+

Therefore we can probably just change this:

for FILE in .github/workflows/*.yaml; do
  sed_runner "s/dask-cuda.git@branch-[^\"\s]\+/dask-cuda.git@branch-${NEXT_SHORT_TAG}/g" ${FILE};
done

to this:

for FILE in .github/workflows/*.yaml; do
  sed_runner "s/dask-cuda.git@branch-[0-9][0-9].[0-9][0-9]/dask-cuda.git@branch-${NEXT_SHORT_TAG}/g" ${FILE};
done

[msadang]

LGTM

[galipremsagar]

/merge