Closed tmr111116 closed 2 weeks ago
The file timestamp on the release page appears newer, so it may have been re-uploaded.
That might be the reason. Once we recorded a particular artifact, we're skipping it in subsequent runs.
The checksums are there to detect tampering with the artifacts after all. So this confirmed it's working. 😉
Thank you for addressing this issue. I was able to install it without any warnings this time. Your prompt response is greatly appreciated!
I encountered a checksum warning when trying to install temurin-17.0.13+11 using
asdf
.The file
OpenJDK17U-jdk_aarch64_mac_hotspot_17.0.13_11.tar.gz.sha256.txt
on the release page (https://github.com/adoptium/temurin17-binaries/releases/tag/jdk-17.0.13%2B11) shows:This checksum does not match the one in this repository:
https://github.com/joschi/java-metadata/blob/677b46b811d9a4030c7200c658217320ccd9679a/docs/checksums/temurin/OpenJDK17U-jdk_aarch64_mac_hotspot_17.0.13_11.tar.gz.sha256#L1
The file timestamp on the release page appears newer, so it may have been re-uploaded.