Checked out a @rustlang cargo project w/ a Cargo.lock. Ran cargo build and Cargo.lock was rewritten w/ diff versions. Is this broken?
-
-
Replying to @duelinmarkers
I thought the whole point of Cargo.lock was to get me the same versions of
@rustlang deps that had previously been used.2 replies 0 retweets 0 likes -
-
Replying to @rustlang
https://github.com/sunng87/cargo-release … is the project. https://gist.github.com/duelinmarkers/fcb8b0da4e905c9c5d6f0590f1219399 … is the local diff.
3 replies 0 retweets 1 like -
Replying to @duelinmarkers @rustlang
I noticed that the versions of direct deps in Cargo.toml are older than the committed Cargo.lock (and my local version). Relevant?
1 reply 0 retweets 0 likes -
Replying to @duelinmarkers @rustlang
It has to do with allow semver compatible updates. Use `=num` to pin specific versions. http://doc.crates.io/specifying-dependencies.html#specifying-dependencies-from-cratesio …
1 reply 0 retweets 0 likes
yes, the default is ^ not =. But if a Cargo.lock exists, it should be used unless "cargo update" is run
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.