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?