Cargo format and clippy

.github/workflows/sdk-ci.yaml

@@ -1,4 +1,4 @@
-name: Python/Kotlin CI
+name: Python/Kotlin/Java CI
 on:
   pull_request:
   workflow_dispatch:

.github/workflows/sdk-release.yaml

@@ -1,4 +1,4 @@
-name: Python/Kotlin Release
+name: Python/Kotlin/Java Release
 on:
   # https://docs.github.com/en/developers/webhooks-and-events/webhook-events-and-payloads#release
   # The Bump Version workflow will make a Github release if it isn't a prerelease version

README.md

@@ -13,7 +13,7 @@ to protect the private or sensitive data your apps process.
 
 ## Language Support
 
-- [Java](https://central.sonatype.com/artifact/com.ironcorelabs/ironcore-alloy)
+- [Java](https://central.sonatype.com/artifact/com.ironcorelabs/ironcore-alloy-java)
 - [Kotlin](https://central.sonatype.com/artifact/com.ironcorelabs/ironcore-alloy)
 - [Python](https://pypi.org/project/ironcore-alloy)
 - Rust - Depend on this repo using a git dependency.

RELEASING.md

@@ -1,6 +1,6 @@
 # Release Checklist
 
-- Update to the new version number using the [Bump Version](https://github.com/IronCoreLabs/ironcore-alloy/actions/workflows/bump-version.yaml) workflow. This will be used as the Rust/Python/Kotlin version number.
-- The [Python/Kotlin Release](https://github.com/IronCoreLabs/ironcore-alloy/actions/workflows/sdk-release.yaml) action will automatically publish the Python/Kotlin SDKs.
+- Update to the new version number using the [Bump Version](https://github.com/IronCoreLabs/ironcore-alloy/actions/workflows/bump-version.yaml) workflow. This will be used as the Rust/Python/Kotlin/Java version number.
+- The [Python/Kotlin/Java Release](https://github.com/IronCoreLabs/ironcore-alloy/actions/workflows/sdk-release.yaml) action will automatically publish the Python/Kotlin/Java SDKs.
 - When the JVM artifacts have been deployed, go to https://oss.sonatype.org, log in using the `icl-devops` username and
-  password from `sonatype-info.txt`, and find the new release in the _Staging Repositories_. Close that repository and then release it in order to actually push the package out to the public repo.
+  password from `sonatype-info.txt`, and find the new release in the _Staging Repositories_. Close that repository and then release it in order to actually push the package out to the public repo.

src/saas_shield/standard_attached.rs

@@ -60,7 +60,7 @@ impl StandardAttachedDocumentOps for SaasShieldStandardAttachedClient {
     ) -> Result<PlaintextAttachedDocument, AlloyError> {
         decrypt_core(&self.standard_client, attached_document, metadata)
             .await
-            .map(|x| PlaintextAttachedDocument(x))
+            .map(PlaintextAttachedDocument)
     }
 
     /// Decrypt multiple documents that were encrypted with the provided metadata.

src/standalone/standard_attached.rs

@@ -57,7 +57,7 @@ impl StandardAttachedDocumentOps for StandaloneStandardAttachedClient {
     ) -> Result<PlaintextAttachedDocument, AlloyError> {
         decrypt_core(&self.standard_client, encrypted_document, metadata)
             .await
-            .map(|x| PlaintextAttachedDocument(x))
+            .map(PlaintextAttachedDocument)
     }
 
     /// Decrypt multiple documents that were encrypted with the provided metadata.