Skip to content

chore(deps): update ghcr.io/sksat/cargo-chef-docker docker tag to v1.84.0 #1985

chore(deps): update ghcr.io/sksat/cargo-chef-docker docker tag to v1.84.0

chore(deps): update ghcr.io/sksat/cargo-chef-docker docker tag to v1.84.0 #1985

Triggered via pull request March 1, 2024 23:44
Status Success
Total duration 1m 57s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
accessing first element with `records.get(0)`: src/dns.rs#L94
warning: accessing first element with `records.get(0)` --> src/dns.rs:94:17 | 94 | let r = records.get(0).unwrap(); | ^^^^^^^^^^^^^^ help: try: `records.first()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#get_first = note: `#[warn(clippy::get_first)]` on by default
this `MutexGuard` is held across an `await` point: src/api.rs#L21
warning: this `MutexGuard` is held across an `await` point --> src/api.rs:21:21 | 21 | let data = &mut data.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/api.rs:24:86 | 24 | let subdomain = subdomain::add(&data.api_client, &params.subdomain, &params.url).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
rust: src/api.rs#L21
[clippy] reported by reviewdog 🐶 this `MutexGuard` is held across an `await` point Raw Output: src/api.rs:21:21: warning: this `MutexGuard` is held across an `await` point (clippy::await_holding_lock)
rust: <unknown>#L1
[clippy] reported by reviewdog 🐶 2 warnings emitted Raw Output: <unknown>:1:1: warning: 2 warnings emitted ()
rust: src/dns.rs#L94
[clippy] reported by reviewdog 🐶 accessing first element with `records.get(0)` Raw Output: src/dns.rs:94:17: warning: accessing first element with `records.get(0)` (clippy::get_first)
rust
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions-rs/[email protected], sksat/rust-cargo-make@add-makers, Swatinem/[email protected], actions-rs/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
rust
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/[email protected], sksat/rust-cargo-make@add-makers, actions-rs/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
rust
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
rust
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
rust
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
rust
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/