rust-cache VS audit-check

In Github Actions we use swatinem/rust-cache. They have a pretty good explanation of what they are doing, and if that's not enough you can have a look at what the code is doing

Out of curiosity, does this play well with the Swatinem/rust-cache action? To improve CI cache performance, it's good practice to cache only dependencies' artifacts, and this action as such automatically cleans out the workspace local artifacts before populating the cache.

I've migrated to https://github.com/dtolnay/rust-toolchain for managing rustup, and https://github.com/Swatinem/rust-cache for caching

I'd also like to drop a recommendation to use https://github.com/Swatinem/rust-cache for caching cargo-related artifacts. I found it to be extremely pleasant to use and very easy to integrate into my CI pipelines.

There is an awesome github actions plugin that configures caching for `~/.cargo` and `target/`: https://github.com/Swatinem/rust-cache

Really cool! A few ideas: - cargo publish it! It'd be good to set the license, description, repository, and readme fields in Cargo.toml. - Your lib.rs looks good - clean & simply exporting types. - You could consider exporting Point/PointN at your library root (e.g. pub use them in lib.rs). If you expect a type will pretty much always be used, it's nice to export it at the root. It also makes those types easier to find on docs.rs. - There is a nifty github actions plugin that caches the crates.io registry, and your dependencies: https://github.com/Swatinem/rust-cache.

I hit a roadblock while trying to integrate audit-check into my actix-yew-template so I forked his github-action: https://github.com/security-union/audit-check