requires a Cargo.lock file

[mimoo]

There are errors if you don't have a Cargo.lock file, which is common if your repo is a library.

[gmemstr]

Yep, this is on me. It was only recently that I realized the use case for the Cargo.lock file (given my knowledge of Node/npm/yarn, I assumed it was beneficial in all cases to have it committed). @mimoo Do you believe relying only on the Cargo.toml file is enough? Or should we try to support both through a parameter.

[mimoo]

Is the Cargo.lock file used for caching? In that case yeah I think relying on Cargo.toml could be a good idea, it's just that the cache is going to become invalidated more often (with each patch version increase, for example) but I don't see any way around that.

[gmemstr]

Correct - it's used as a primary part of the cache key. But if it's not committed the cache will never be loaded.

[mimoo]

Interesting, I think a better way to handle that in Rust would be to just use the latest cache used to build master

[marboledacci]

I see this issue is old, please update if this is still required and provide more details, or close it.