You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The Rust 1.45.0 CI job has started failing due to an update of the serde and serde_derive crates. The latest updates to these crates causes cargo to require the resolver feature which was unstable in the version of cargo shipped in the Rust 1.45.0 toolchain.
This feature was stabilized in the version of cargo shipped with the Rust 1.51.0 toolchain.
Example of failure:
cargo build --all-targets
warning: /src/rust-url/url/Cargo.toml: unused manifest key: package.rust-version
warning: /src/rust-url/data-url/Cargo.toml: unused manifest key: package.rust-version
warning: /src/rust-url/percent_encoding/Cargo.toml: unused manifest key: package.rust-version
warning: /src/rust-url/idna/Cargo.toml: unused manifest key: package.rust-version
warning: /src/rust-url/form_urlencoded/Cargo.toml: unused manifest key: package.rust-version
error: failed to download `serde v1.0.143`
Caused by:
unable to get packages from source
Caused by:
failed to parse manifest at `/home/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/serde-1.0.143/Cargo.toml`
Caused by:
feature `resolver` is required
this Cargo does not support nightly features, but if you
switch to nightly channel you can add
`cargo-features = ["resolver"]` to enable this feature
The Cargo.toml specified in the build failure now includes the manifest key, resolver = "1".
The text was updated successfully, but these errors were encountered:
Describe the bug
The Rust 1.45.0 CI job has started failing due to an update of the
serde
andserde_derive
crates. The latest updates to these crates causes cargo to require theresolver
feature which was unstable in the version of cargo shipped in the Rust 1.45.0 toolchain.This feature was stabilized in the version of cargo shipped with the Rust 1.51.0 toolchain.
Example of failure:
The
Cargo.toml
specified in the build failure now includes the manifest key,resolver = "1"
.The text was updated successfully, but these errors were encountered: