-
Notifications
You must be signed in to change notification settings - Fork 211
run cargo update #2788
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run cargo update #2788
Conversation
syphar
commented
Apr 6, 2025
Updating async-compression v0.4.21 -> v0.4.22 Updating aws-config v1.6.0 -> v1.6.1 Updating aws-lc-rs v1.12.6 -> v1.13.0 Updating aws-lc-sys v0.27.1 -> v0.28.0 Updating aws-sdk-cloudfront v1.68.0 -> v1.70.0 Updating aws-sdk-s3 v1.79.0 -> v1.82.0 Updating aws-sdk-sso v1.62.0 -> v1.64.0 Updating aws-sdk-ssooidc v1.63.0 -> v1.65.0 Updating aws-sdk-sts v1.63.0 -> v1.65.0 Updating aws-smithy-http-client v1.0.0 -> v1.0.1 Adding aws-smithy-observability v0.1.2 Updating aws-smithy-runtime v1.8.0 -> v1.8.1 Updating axum v0.8.1 -> v0.8.3 Updating axum-core v0.5.0 -> v0.5.2 Updating axum-extra v0.10.0 -> v0.10.1 Updating borsh v1.5.6 -> v1.5.7 Updating cc v1.2.16 -> v1.2.18 Updating clap v4.5.32 -> v4.5.35 Updating clap_builder v4.5.32 -> v4.5.35 Updating crates-index v3.7.0 -> v3.8.0 Updating darling v0.20.10 -> v0.20.11 Updating darling_core v0.20.10 -> v0.20.11 Updating darling_macro v0.20.10 -> v0.20.11 Updating errno v0.3.10 -> v0.3.11 Updating flate2 v1.1.0 -> v1.1.1 Updating gix-features v0.41.0 -> v0.41.1 Updating gix-packetline-blocking v0.18.2 -> v0.18.3 Updating hyper-util v0.1.10 -> v0.1.11 Updating iana-time-zone v0.1.61 -> v0.1.63 Updating icu_locid_transform_data v1.5.0 -> v1.5.1 Updating icu_normalizer_data v1.5.0 -> v1.5.1 Updating icu_properties_data v1.5.0 -> v1.5.1 Updating indexmap v2.8.0 -> v2.9.0 Updating jobserver v0.1.32 -> v0.1.33 Updating log v0.4.26 -> v0.4.27 Updating miniz_oxide v0.8.5 -> v0.8.7 Updating once_cell v1.21.1 -> v1.21.3 Updating prettyplease v0.2.31 -> v0.2.32 Updating redox_syscall v0.5.10 -> v0.5.11 Updating rustix v1.0.3 -> v1.0.5 Updating rustls-webpki v0.103.0 -> v0.103.1 Updating smallvec v1.14.0 -> v1.15.0 Updating socket2 v0.5.8 -> v0.5.9 Updating string_cache v0.8.8 -> v0.8.9 Updating tempfile v3.19.0 -> v3.19.1 Updating time v0.3.40 -> v0.3.41 Updating time-macros v0.2.21 -> v0.2.22 Updating tokio v1.44.1 -> v1.44.2 Updating whoami v1.5.2 -> v1.6.0 Adding windows-core v0.61.0 Adding windows-implement v0.60.0 Adding windows-interface v0.59.1 Adding windows-strings v0.4.0 Updating zerocopy v0.8.23 -> v0.8.24 Updating zerocopy-derive v0.8.23 -> v0.8.24 Updating zip v2.4.2 -> v2.6.1 Updating zstd-safe v7.2.3 -> v7.2.4 Updating zstd-sys v2.0.14+zstd.1.5.7 -> v2.0.15+zstd.1.5.7
CI is failing, is it expected? |
the audit failing is expected right now, because of #2783 / #2784. Would be solved with frewsxcv/rust-crates-index#190 and frewsxcv/rust-crates-index#190, though depending on when @Byron has time for these I'll add an ignore-statement to the rustsec report. ( I also didn't dig deeper into what exactly the security risk was and if we were affected at all with the crates-index repo) |
Sorry for the unusual wait, but these are unusual times 😁. |
superseded by #2791 |