chore: fix clippy warnings (#308)

Co-authored-by: Fabian-Lars <118197967+FabianLars-crabnebula@users.noreply.github.com>
Co-authored-by: FabianLars-crabnebula <fabianlars@crabnebula.dev>

Author: rex4539

bindings/packager/nodejs/src-ts/config.d.ts

@@ -429,12 +429,10 @@ export interface MacOsConfig {
    * Path to the Info.plist file for the package.
    */
   infoPlistPath?: string | null;
-
   /**
    * Path to the embedded.provisionprofile file for the package.
    */
   embeddedProvisionprofilePath?: string | null;
-
   /**
    * Apps that need to be packaged within the app.
    */

crates/packager/src/cli/signer/mod.rs

@@ -24,7 +24,7 @@ pub struct Options {
 
 pub fn command(options: Options) -> Result<()> {
     match options.command {
-        Commands::Sign(opts) => sign::command(opts).map_err(Into::into),
+        Commands::Sign(opts) => sign::command(opts),
         Commands::Generate(opts) => generate::command(opts),
     }
 }

crates/packager/src/codesign/windows.rs

@@ -83,10 +83,7 @@ static SIGN_TOOL: Lazy<crate::Result<PathBuf>> = Lazy::new(|| {
     let mut installed_kits: Vec<String> = installed_roots_key
         .enum_keys()
         /* Report and ignore errors, pass on values. */
-        .filter_map(|res| match res {
-            Ok(v) => Some(v),
-            Err(_) => None,
-        })
+        .filter_map(|res| res.ok())
         .collect();
 
     // Sort installed kits

crates/updater/src/lib.rs

@@ -51,12 +51,12 @@
 //!
 //! ## Endpoint Response
 //!
-//! The updater expects the endpoint to respond with 2 possible reponses:
+//! The updater expects the endpoint to respond with 2 possible responses:
 //!
 //! 1. [`204 No Content`](https://datatracker.ietf.org/doc/html/rfc2616#section-10.2.5) in case there is no updates available.
 //! 2. [`200 OK`](https://datatracker.ietf.org/doc/html/rfc2616#section-10.2.1) and a JSON response that could be either a JSON representing all available platform updates
-//!     or if using endpoints variables (see above) or a header to attach the current updater target,
-//!     then it can just return information for the requested target.
+//!    or if using endpoints variables (see above) or a header to attach the current updater target,
+//!    then it can just return information for the requested target.
 //!
 //! The JSON response is expected to have these fields set:
 //!