fix: Attempting to use pre-generated bindgens for the aws-lc-sys library

2025-09-12 20:42:19 -06:00
parent b29f33413a
commit 3a1752b148
3 changed files with 4 additions and 46 deletions
@@ -8,48 +8,4 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.0.1] - 2025-09-10

 ### Other
- Initial test release of the `gman` project.
-## v0.0.5 (2025-09-12)
-
-### Fix
-
- Install openSSL differently to make this work
-
-## v0.0.4 (2025-09-12)
-
-### Fix
-
- Address edge case for unknown_musl targets
-
-## v0.0.3 (2025-09-12)
-
-### Fix
-
- Install LLVM prereqs for release flow
-
-## v0.0.2 (2025-09-12)
-
-### Fix
-
- 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
+- Initial test release of the `gman` project.