ci: use cross for musl builds

.github/workflows/release.yml

@@ -308,13 +308,31 @@ jobs:
           esac
 
       - name: Build
-        run: cargo build --release --verbose --target=${{ matrix.job.target }} --locked
+        shell: bash
+        run: |
+          set -euxo pipefail
+          if [[ "${{ matrix.job.use-cross || 'false' }}" == 'true' ]]; then
+            cross build --release --locked --target=${{ matrix.job.target }} --verbose
+          else
+            cargo build --release --locked --target=${{ matrix.job.target }} --verbose
+          fi
 
       - name: Verify file
         shell: bash
         run: |
           file target/${{ matrix.job.target }}/release/gman
 
+      - name: Test
+        if: matrix.job.target != 'aarch64-apple-darwin' && matrix.job.target != 'aarch64-pc-windows-msvc'
+        shell: bash
+        run: |
+          set -euxo pipefail
+          if [[ "${{ matrix.job.use-cross || 'false' }}" == 'true' ]]; then
+            cross test --release --locked --target=${{ matrix.job.target }} --verbose ${{ matrix.job.test-bin }}
+          else
+            cargo test  --release --locked --target=${{ matrix.job.target }} --verbose ${{ matrix.job.test-bin }}
+          fi
+
       - name: Test
         if: matrix.job.target != 'aarch64-apple-darwin' && matrix.job.target != 'aarch64-pc-windows-msvc'
         run: cargo test --release --verbose --target=${{ matrix.job.target }} ${{ matrix.job.test-bin }}

CHANGELOG.md

@@ -9,35 +9,3 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Other
 - Initial test release of the `gman` project.
-
-## v0.0.2 (2025-09-13)
-
-### Fix
-
-- Revert back hacky stuff so I can test with act now
-- Attempting to use pre-generated bindgens for the aws-lc-sys library
-- Install openSSL differently to make this work
-- Address edge case for unknown_musl targets
-- Install LLVM prereqs for release flow
-- Updated the release flow to install the external bindgen-cli
-
-## v0.0.1 (2025-09-12)
-
-### Feat
-
-- Azure Key Vault support
-- GCP Secret Manager support
-- Full AWS SecretsManager support
-- AWS Secrets Manager support
-- Added two new flags to output where gman writes logs to and where it expects the config file to live
-
-### Fix
-
-- Made the vault file location more fault tolerant
-- Attempting to maybe be a bit more explicit about config file handling to fix MacOS tests
-
-### Refactor
-
-- Refactor configuration structs directly into the provider definition to simplify validation, structs, and future extensions
-- Made the creation of the log directories a bit more fault tolerant
-- Renamed the provider field in a config file to type to make things a little easier to understand; also removed husky

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "gman"
-version = "0.0.2"
+version = "0.0.1"
 edition = "2024"
 authors = ["Alex Clarke <alex.j.tusa@gmail.com>"]
 description = "Universal secret management and injection tool"