From cee6ddf3fb88a4cc19baddf3a62c947166983f3a Mon Sep 17 00:00:00 2001 From: Binglin Chang Date: Wed, 21 Oct 2026 03:42:29 +0000 Subject: [PATCH] elosdb: install pins v0.1.12 (aarch64 ece4fca4, x86_64 d9b49a7e) --- elosdb/install | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/elosdb/install b/elosdb/install index cbfa6aaa3e..4f3bd5dfc2 100755 --- a/elosdb/install +++ b/elosdb/install @@ -17,13 +17,13 @@ cd "$(dirname "$0")" # THE RELEASE THIS SUBMISSION IS, PER ARCHITECTURE: a tag and that tag's asset digest, # pinned here, and a pair moves together or not at all. The two arches may name # different tags — each pins the release that carries ITS asset and was measured with -# it (v0.1.10 carries both: the aarch64 asset built on an aarch64 box, the x86_64 asset +# it (v0.1.12 carries both: the aarch64 asset built on an aarch64 box, the x86_64 asset # on an x86 box, from the same source). An empty digest means no asset for that arch, # and install refuses below rather than fetching a file it cannot check. -RELEASE_TAG_aarch64="v0.1.10" -RELEASE_SHA256_aarch64="44d2a66dca85d28d2fffdc439006f1a348461f50450b446b8e7791957741fa70" -RELEASE_TAG_x86_64="v0.1.10" -RELEASE_SHA256_x86_64="ce12bbf75774b4690602ea782aa0961d6f5e4a6d146078d31427bed893b719b5" +RELEASE_TAG_aarch64="v0.1.12" +RELEASE_SHA256_aarch64="ece4fca40217d5430855ccd643c01804b107ef6f3c5eeeab971bb663a69b9aba" +RELEASE_TAG_x86_64="v0.1.12" +RELEASE_SHA256_x86_64="d9b49a7e79e1ed93c51996cc34e125cfde531d42201376ca228496b59783e205" release_url() { echo "https://github.com/decster/elosdb/releases/download/$2/elosdb-$2-linux-$1"; } # THE ARTIFACT NAMES ITS ARCHITECTURE AND ITS CORE. aarch64 is built -mcpu=neoverse-v2