Skip to content

Commit 448122a

Browse files
authored
chore(dev/release): embed hash of source tarball into email (#675)
Following the discussion on https://lists.apache.org/thread/o2mpsf5okhzfz2k4mbg5d4s9ror69587 and apache/arrow-adbc#3965, I figured we should do the same for arrow-go.
1 parent 7d9f381 commit 448122a

File tree

1 file changed

+17
-4
lines changed

1 file changed

+17
-4
lines changed

dev/release/release_rc.sh

Lines changed: 17 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -70,11 +70,11 @@ rc_hash="$(git rev-list --max-count=1 "${rc_tag}")"
7070
id="apache-arrow-go-${version}"
7171
tar_gz="${id}.tar.gz"
7272

73-
if [ "${RELEASE_SIGN}" -gt 0 ]; then
74-
git_origin_url="$(git remote get-url origin)"
75-
repository="${git_origin_url#*github.com?}"
76-
repository="${repository%.git}"
73+
git_origin_url="$(git remote get-url origin)"
74+
repository="${git_origin_url#*github.com?}"
75+
repository="${repository%.git}"
7776

77+
if [ "${RELEASE_SIGN}" -gt 0 ]; then
7878
echo "Looking for GitHub Actions workflow on ${repository}:${rc_tag}"
7979
run_id=""
8080
while [ -z "${run_id}" ]; do
@@ -109,6 +109,15 @@ if [ "${RELEASE_UPLOAD}" -gt 0 ]; then
109109
"${tar_gz}.asc"
110110
fi
111111

112+
gh release download "${rc_tag}" \
113+
--dir . \
114+
--pattern "${tar_gz}.sha512" \
115+
--repo "${repository}" \
116+
--clobber
117+
118+
SOURCE_TARBALL_HASH=$(awk '{print $1}' "${tar_gz}.sha512")
119+
rm -f "${tar_gz}.sha512"
120+
112121
echo "Draft email for dev@arrow.apache.org mailing list"
113122
echo ""
114123
echo "---------------------------------------------------------"
@@ -126,6 +135,10 @@ ${rc_hash} [1]
126135
127136
The source release rc${rc} is hosted at [2].
128137
138+
This is not a permanent URL. If the RC is accepted, it will be moved to
139+
the final release location. The SHA512 hash of the source tarball is:
140+
${SOURCE_TARBALL_HASH}.
141+
129142
Please download, verify checksums and signatures, run the unit tests,
130143
and vote on the release. See [3] for how to validate a release candidate.
131144

0 commit comments

Comments
 (0)