Brendan Cully c4664609ed Use package root as cargo check working directory
Cargo commands are affected by the `.cargo/config` files above
their working directory. If cargo is invoked from above the directory
holding `Cargo.toml`, it may not pick up important settings like
registry replacements, causing it to behave differently or even fail.

Most cargo invocations are currently setting their working directories
to the directory containing `Cargo.toml`, but a couple of paths remain
in which cargo is invoked from the default workspace root instead.

This change fixes that, resolving some cargo check failures that I
experienced in a multi-root workspace in which packages used different
registries.
2021-05-12 19:50:52 -07:00
..
2021-05-11 19:01:39 +00:00
2021-05-12 14:49:43 +00:00
2021-05-12 14:49:43 +00:00
2021-05-12 14:42:01 +00:00
2021-05-10 20:10:59 +00:00
2021-04-18 02:14:27 +00:00
2021-05-08 23:14:08 +02:00
2021-04-06 16:22:26 +03:00
2021-05-06 20:12:15 +03:00
2021-05-10 15:25:56 +03:00
2021-03-21 16:15:41 +01:00