Thomas Eizinger

We've now migrated to the provided GitHub action and semver-checking takes about 15 minutes for us. See https://github.com/libp2p/rust-libp2p/actions/runs/6068173889/job/16460787944#step:4:210. We have some interoperability tests that also take similarly long but the...

My workflow doesn't build it for the baseline version, no. I thought that one was downloaded from docs.rs or something? Does it build the baseline version also locally? I am...

> make `cargo-semver-checks` aware of the possibility of the baseline rustdoc JSON already being generated so it only rebuilds when necessary. I think this is the MVP. As long as...

I just saw that there is already `target/semver-checks` but that directory is 21GB after a `cargo clean` and running `cargo semver-checks check-release --workspace`. We can't cache that :sweat_smile:

> Perhaps something like a `--baseline-cache ` option, where `cargo-semver-checks` will move built baseline JSON files into that directory, or use existing files if they are there? Just separating them...

> * How big are all the JSON files from those `doc` directories? That's the only part we absolutely need, and we can avoid caching everything else. ``` > stat...

> > Just separating them from the current compilation output would already be good. That would allow us to clean that target directory of artifacts and cache it. > >...

> > That is a 110MB! > > Whew, I'm glad it's that little :) It's also JSON so it should be highly compressible with zstd which GitHub Actions will...

> > > That is a 110MB! > > > > > > Whew, I'm glad it's that little :) It's also JSON so it should be highly compressible with...

> > > to make this really effective, `cargo semver-checks` would have to move the JSON files into that `cache` directory itself and clean the target directory afterwards > >...