Skip to content
CI (Linux)

fix(deps): update rust crate serde to ~1.0.178 #2528

Sign in to view logs

fix(deps): update rust crate serde to ~1.0.178

fix(deps): update rust crate serde to ~1.0.178 #2528

Triggered via pull request July 27, 2023 21:56
@renovaterenovate[bot]
synchronize #300
renovate/serde-1.x
Status Success
Total duration 2m 12s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

linux.yml

on: pull_request
Matrix: build_and_test
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
nightly - x86_64-unknown-linux-gnu
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
nightly - x86_64-unknown-linux-gnu
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/
nightly - x86_64-unknown-linux-gnu
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/
nightly - x86_64-unknown-linux-gnu
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/
nightly - x86_64-unknown-linux-gnu
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/
nightly - x86_64-unknown-linux-gnu
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
nightly - x86_64-unknown-linux-gnu
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
nightly - x86_64-unknown-linux-gnu
spurious network error (3 tries remaining): [55] Failed sending data to the peer
nightly - x86_64-unknown-linux-gnu
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/equivalent/equivalent-1.0.1.crate` (146.75.106.137), got 502
nightly - x86_64-unknown-linux-gnu
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/unicase/unicase-2.6.0.crate` (146.75.106.137), got 502