Add option to not use Cargo.lock hash

[yonathan06]

Is there a way to not include the Cargo.toml/Cargo.lock (or any file) hash in the cache key?

I have a build workflow that is triggered on a new version, the the Cargo.toml/Cargo.lock are always different between builds, and so the cache key, so it is ineffective for my use case, is there a way to disable it?

[rekby]

Is shared-key option solved your task?

[yonathan06]

shared-key adds the string to the key, but doesn't remove the hash

[Swatinem]

Currently there is no way to completely disable this part of the key. But it shouldn’t be such a big problem either, as it falls back to the key prefix without the Cargo.lock portion and reuses caches anyway after cleaning them.

[yonathan06]

Does it also drop Cargo.toml hash as well? because I update the version of the package, so the hash definitely changes