Are environment variables for cargo inherited?

[thomaseizinger]

We've recently moved from GitHub's runners to self-hosted runners and are experiencing timeouts when cargo semver-checks tries to update the registry index. For example: https://github.com/libp2p/rust-libp2p/actions/runs/4819569817/jobs/8582952664

We already use the sparse registry protocol but I am wondering whether that also applies for the cargo invocations made by cargo semver-checks?

[obi1kenobi]

I think they should be inherited (I've seen the color=always env var setting affect inner cargo invocations) but I don't think we have a test for it.

I'd happily merge a PR adding that kind of test into the test suite if you suspect this might be broken, though.

[thomaseizinger]

It was more of a question and we recently haven't seen these errors any more.

Will reopen if it is a problem again!