Allow verifying published MSRV #216
Labels
C-enhancement
Category: A new feature or an improvement for an existing one
help wanted
Call for participation: Help is requested to fix this issue
Packages can have two MSRVs
For example, if you use workspace inheritance, your local development / git dependency MSRV is 1.64 but your registry dependency MSRV could be lower but you can't verify it. This is because
cargo package
removes these development-time features.We could verify the published version of a package if we did
cargo package
on each package and then verified the.crate
files.The text was updated successfully, but these errors were encountered: