I copied the gihub actions caching configuration from examples, and I'm
not sure it's optimal. In particular, it causes a cache miss whenever
any Cargo.lock changes. I suspect that it would be better to always
hit the cache, and let cargo figure out what it needs to rebuild.
I copied the gihub actions caching configuration from examples, and I'm not sure it's optimal. In particular, it causes a cache miss whenever any
Cargo.lock
changes. I suspect that it would be better to always hit the cache, and let cargo figure out what it needs to rebuild.type: development