-
Notifications
You must be signed in to change notification settings - Fork 24
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
Should we verify minimal dependency versions #25
Comments
The downside is the brittleness of dependencies if they aren't also verifying it. |
I think this should be an opt-in stage. Not sure what Rust version it should be run on (does it require nightly atm?). |
I think you can use unstable flags without nightly but I'm unsure. I at least do it with libtest's json output. |
As for best practices, I am unsure. I've seen discussions around this but haven't adopted it myself (yet). I've been tempted to adopt it due to minrust issues. |
Relevant: rust-lang/api-guidelines#123 |
Closing this in favor of #78. |
cargo has an unstable flag to calculate dependencies using the minimum rather than the maximum version. This verifies that
Cargo.toml
s are not stale.The text was updated successfully, but these errors were encountered: