warning: this `MutexGuard` is held across an `await` point --> src/main.rs:47:9 | 47 | let mut cache = cache.lock().unwrap(); | ^^^^^^^^^ | = help: consider using an async-aware `Mutex` type or ensuring the `MutexGuard` is dropped before calling await note: these are all the `await` points this lock is held through --> src/main.rs:57:10 | 57 | .await | ^^^^^ ... 71 | .await | ^^^^^ = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#await_holding_lock = note: `#[warn(clippy::await_holding_lock)]` on by default

warning: field `0` is never read --> src/errors/fetcher.rs:9:19 | 9 | InvalidSha256(usize), | ------------- ^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 9 | InvalidSha256(()), | ~~

warning: field `0` is never read --> src/errors/fetcher.rs:8:18 | 8 | ReqwestError(reqwest::Error), | ------------ ^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 8 | ReqwestError(()), | ~~

warning: field `0` is never read --> src/errors/fetcher.rs:7:15 | 7 | OctoError(octocrab::Error), | --------- ^^^^^^^^^^^^^^^ | | | field in this variant | help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 7 | OctoError(()), | ~~

warning: field `0` is never read --> src/errors/api.rs:24:14 | 24 | Extrenal(String), | -------- ^^^^^^ | | | field in this variant | = note: `#[warn(dead_code)]` on by default help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field | 24 | Extrenal(()), | ~~

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions-rs/clippy-check@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.