[BUG] Inconsistent contents between release artifacts.

[shanduur]

Describe the bug Tarballs (even for the same system) have inconsistent contents, which can be seen in Linux GNU for both aarch64 and x86_64.

To Reproduce

$ curl -sL "https://github.com/amber-lang/amber/releases/download/0.4.0-alpha/amber-x86_64-unknown-linux-gnu.tar.xz" > x86_64.tar.gz
$ curl -sL "https://github.com/amber-lang/amber/releases/download/0.4.0-alpha/amber-aarch64-unknown-linux-gnu.tar.xz" > aarch64.tar.gz
$ tar -tf aarch64.tar.gz 
amber
$ tar -tf x86_64.tar.gz 
amber-x86_64-unknown-linux-gnu/
amber-x86_64-unknown-linux-gnu/README.md
amber-x86_64-unknown-linux-gnu/LICENSE.md
amber-x86_64-unknown-linux-gnu/amber

Expected behavior Stable tarbal contents between artifacts.

Additional context n/a

[Mte90]

We need to improve the CI for the aarch64 package https://github.com/amber-lang/amber/blob/staging/.github/workflows/release-linux-arm.yml

What do you think @Ph0enixKM?

[Ph0enixKM]

cargo-dist now supports linux arm release triples which is a great news. We can now remove our release-linux-arm.yml workflow and add:

• aarch64-unknown-linux-gnu
• aarch64-unknown-linux-musl in Cargo.toml where we hold the release triplets

[Mte90]

We worked a lot on our CI but I don't think that we fixed that issue

[Ph0enixKM]

@Mte90 this has been fixed actually. The problem was with our workflow that we had before its full rewrite. Now we ship all contents the same way