Skip to content

Commit bfb1c12

Browse files
committedFeb 22, 2025
fix tools/update_vendor, fix replace 1.minor.patch version
1 parent fcaf602 commit bfb1c12

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed
 

‎docs/instruction-how-to-bump-repository.md

+10-2
Original file line numberDiff line numberDiff line change
@@ -16,14 +16,22 @@ VERSION_FILES=(
1616
LIBRARY_FILES=(
1717
go.mod
1818
providers/go.mod
19+
test/e2e/go.mod
1920
)
2021
```
2122
2. Bump library versions.
2223
```bash
2324
sed -i s/v1.$MINOR_OLD.$PATCH_OLD/v1.$MINOR.$PATCH/ "${VERSION_FILES[@]}"
2425
sed -i s/v0.$MINOR_OLD.$PATCH_OLD/v0.$MINOR.$PATCH/ "${LIBRARY_FILES[@]}"
25-
go mod tidy
26-
./tools/update_version.sh
26+
sed -i s/v1.$MINOR_OLD.$PATCH_OLD/v1.$MINOR.$PATCH/ "${LIBRARY_FILES[@]}"
27+
for go_mod_file in "${LIBRARY_FILES[@]}"; do
28+
dir=$(dirname "$go_mod_file")
29+
pushd $dir
30+
echo "Tidying $dir"
31+
go mod tidy
32+
popd
33+
done
34+
./tools/update_vendor.sh
2735
```
2836
3. In [WORKSPACE](https://github.com/kubernetes/cloud-provider-gcp/blob/master/WORKSPACE), update `fetch_kube_release` sha to the desired release version.
2937
* Note: The current Kubernetes release is using sha512 hash while cloud-provider-gcp is using sha256. Re-sha with command `sha256sum` if needed. Use this command to generate values automatically.

0 commit comments

Comments
 (0)
Please sign in to comment.