The build-dir is changing and we need help with people testing it for issues, particularly in identifying tools and processes that rely on unspecified implementation details of Cargo.
While the Cargo team does not officially endorse sharing a build-dir across workspaces, [---]
Pardon my ignorance, but should this be read as "If you set a (global) build.target-dir in ~/.cargo/config.toml, and then build two different projects that use workspaces, then you will anger the Rust Gods"?
Not quite sure what you are getting at but build.build-dir is what you should set for a global or shared build cach and not build.target-dir as it avoids builds from colliding and makes final artifacts accessible. This is a relatively new addition though.