From c7ae161a39c29656938ce1c8d4f674e387980022 Mon Sep 17 00:00:00 2001 From: KtorZ Date: Wed, 2 Oct 2024 12:08:01 +0200 Subject: [PATCH] Mention quirks about gnu/musl linux artifact in the release guidelines. --- CONTRIBUTING.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3e3bdc3b..78068b77 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -101,6 +101,14 @@ The process follows these steps: > tag-name = "v{{version}}" > ``` +> [!IMPORTANT] +> +> Since v1.1.4, we have switched to producing statically linked binary with musl, preventing issues with openssl on various linux platforms. However, this changes the artifact name +> from: `aiken-x86_64-unknown-linux-gnu.tar.gz` to `aiken-x86_64-unknown-linux-musl.tar.gz`. Consequently, we've patched `aikup` in version v0.0.11, but people using previous +> version will fail to install aiken through aikup. So for a little a while, we need to manually re-upload a `-gnu.tar.gz` archive (which can be obtained by simply renaming the musl one) so that aikup can keep fetching artifacts on Linux prior to version `v0.0.11`. We can cease doing that once enough time has reasonably passed and enough people have switched to aikup. +> +> Ideally, we should introduce an `upgrade` command to aikup, and have some kind of notification system that indicates to people that they should upgrade their aikup installer. + ## About Issues ### :bug: How To Report A Bug