-
Notifications
You must be signed in to change notification settings - Fork 88
Cargo-minimal.lock and Cargo-recent.lock have the same contents. Is this right? #454
Copy link
Copy link
Open
Labels
questionFurther information is requestedFurther information is requested
Description
sha256sum Cargo-minimal.lock Cargo-recent.lock
cfc03189fb6e75ba99b0b74b0abf46e942c96c99ef2266538e99d7a7ec746ffb Cargo-minimal.lock
cfc03189fb6e75ba99b0b74b0abf46e942c96c99ef2266538e99d7a7ec746ffb Cargo-recent.lock
I have been running ./contrib/update-lock-files.sh once to get CI to pass thinking it automatically handled locking MSRV dependencies. But I don't see that they're actually different.
- Check the commit log to see where they unified, if ever
- The initial commit from Add Cargo-{minimal,recent}.lock to test deps #357 20208ec has them unified
- If not, describe how our CI passes MSRV tests without locking
- Both lock files have sufficiently low dependencies that they pass MSRV, e.g. reqwest 0.12.4 (tested with `cargo +1.63 build --locked)
- Fix the script to accommodate MSRV dependency requirements
s/o @nothingmuch for discovering this
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
questionFurther information is requestedFurther information is requested
Type
Projects
Status
No status