This is an automated email from the ASF dual-hosted git repository.
zeroshade pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iceberg-go.git
The following commit(s) were added to refs/heads/main by this push:
new ba15500a infra: release_rc.sh regenerate sha512 file after rename
(#590)
ba15500a is described below
commit ba15500a346762103d6e43a0e4617513e1e1a1e8
Author: Kevin Liu <[email protected]>
AuthorDate: Wed Oct 8 10:24:03 2025 -0700
infra: release_rc.sh regenerate sha512 file after rename (#590)
we cannot reuse the sha512 file from gh release because it referring to
the tar.gz file with -rc suffix
regenerate the sha512 file after rename and then upload to apache svn
Tested generating shasum locally, uploaded to
https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-go-0.4.0-rc1/
and now `dev/release/verify_rc.sh 0.4.0 1` passes
---
dev/release/release_rc.sh | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/dev/release/release_rc.sh b/dev/release/release_rc.sh
index 6d28b0cd..d7861fc1 100755
--- a/dev/release/release_rc.sh
+++ b/dev/release/release_rc.sh
@@ -116,6 +116,11 @@ if [ "${RELEASE_UPLOAD}" -gt 0 ]; then
for fname in ./*; do
mv "${fname}" "${fname//-rc${rc}/}"
done
+
+ # regenerating checksum after rename because the one in gh release refers to
the tar.gz file with -rc suffix
+ echo "Generating SHA512 checksum"
+ tar_gz="apache-iceberg-go-${version}.tar.gz"
+ sha512sum "${tar_gz}" > "${tar_gz}.sha512"
popd
svn import "${id}" "https://dist.apache.org/repos/dist/dev/iceberg/${id}"; -m
"Apache Iceberg Go ${version} RC${rc}"
fi
