fix: remove musl target from cargo-dist due to keyring incompatibility

The keyring crate used for secure-storage has native dependencies that don't
work with musl libc. This causes the x86_64-unknown-linux-musl build to fail
when trying to link OpenSSL.

Solutions considered:
1. Disable secure-storage for musl builds (complex configuration)
2. Use vendored OpenSSL (adds build time and complexity)
3. Remove musl target (chosen - simplest)

The x86_64-unknown-linux-gnu target still provides Linux binaries that work
on most distributions. Users needing static binaries can build manually with
--no-default-features --features full.

Author: joshrotenberg

Cargo.toml

@@ -34,7 +34,8 @@ ci = "github"
 # The installers to generate for each app
 installers = ["shell", "powershell"]
 # Target platforms to build apps for (Rust target-triple syntax)
-targets = ["aarch64-apple-darwin", "x86_64-apple-darwin", "x86_64-unknown-linux-gnu", "x86_64-unknown-linux-musl", "x86_64-pc-windows-msvc"]
+# Note: x86_64-unknown-linux-musl removed due to keyring incompatibility with musl
+targets = ["aarch64-apple-darwin", "x86_64-apple-darwin", "x86_64-unknown-linux-gnu", "x86_64-pc-windows-msvc"]
 # Which actions to run on pull requests
 pr-run-mode = "plan"
 # Whether dist should create a Github Release or use an existing draft

crates/redisctl/Cargo.toml

@@ -66,6 +66,8 @@ full = ["cloud", "enterprise", "upload"]
 cloud = []
 enterprise = []
 upload = ["dep:files-sdk"]
+# Note: secure-storage may not work on musl targets due to keyring native dependencies
+# Build with --no-default-features --features full for musl
 secure-storage = ["dep:keyring"]
 
 [dev-dependencies]