bharos opened a new pull request, #13643:
URL: https://github.com/apache/gravitino/pull/13643
### What changes were proposed in this pull request?
`docs/how-to-sign-releases.md` documents `.sha256` / `shasum -a 256` in five
places. Releases ship `.sha512` — `release-build.sh` generates every checksum
with `shasum -a 512`. Corrected both halves of the page, and refreshed the
examples, which still referenced `gravitino.0.2.0.zip`.
### Why are the changes needed?
Part of #13637
Step 3 of "Verify a Release" is the step meant to prove the artifact
downloaded intact, and as written it cannot succeed: the `.sha256` file does
not exist, and even if it did, a SHA-256 hash would never match a published
SHA-512 one.
### Does this PR introduce _any_ user-facing change?
No, documentation only.
### How was this patch tested?
Ran both commands against a published 1.3.1 artifact.
As the page now reads:
```
$ diff -u gravitino-trino-connector-435-439-1.3.1.tar.gz.sha512 \
<(shasum -a 512 gravitino-trino-connector-435-439-1.3.1.tar.gz)
RESULT: checksum matches
```
As it read before:
```
$ diff -u gravitino-trino-connector-435-439-1.3.1.tar.gz.sha256 \
<(shasum -a 256 gravitino-trino-connector-435-439-1.3.1.tar.gz)
diff: gravitino-trino-connector-435-439-1.3.1.tar.gz.sha256: No such file or
directory
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
