-
Notifications
You must be signed in to change notification settings - Fork 95
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
use cargo_util_schemas::{PackageName, FeatureName} #260
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cargo_metadata
basically consumes the output JSON from cargo metadata
, which should be validated by cargo itself already. I am not sure if I see the value of extra validations in this crate. Could you elaborate why this is needed?
I don't care about the validation, but sharing data types with cargo may be a useful way forward to slowly making cargo_metadata mostly a set of convenience functionality |
CI is failing because [package]
name = "cargo-util-schemas"
version = "0.2.0"
rust-version = "1.75.0" # MSRV:1 https://docs.rs/crate/cargo-util-schemas/0.2.0/source/Cargo.toml.orig So this would be an MSRV bump as well as an API breaking change |
Just a gentle bump on this - under consideration or should it be closed? I will say that having |
That's quite an MSRV bump. What's the earliest rustc version that supports |
1.56, though Cargo's MSRV-aware resolver recognizes it even when the version is older than 1.56. |
Oh neat, thanks! edit: lol we already use |
Oh well, let's bump the rust-version. It's a major version bump, and anyone using an old cargo to compile cargo_metadata to use it on a newer crate is already asking for trouble anyway. |
Interestingly, the "real" MSRV is $ cargo msrv -- cargo check --ignore-rust-version --config='registries.crates-io.protocol="git"'
...
Check for toolchain '1.65.0-x86_64-unknown-linux-gnu' succeeded
Finished The MSRV is: 1.65.0 (which is when I'll push a commit that changes CI and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That leaves two TODOs, introducing PackageName
and RegistryName
, which I'm not confident about - what do you feel is the best course of action there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea I like this. Let's bundle it into the next major release
Testing the waters for how you'd feel about this change
cargo_metadata has validated strings for these usecases.