This would mean that the cargo vendor-filterer path is more separate from the regular vendor path in the release script. Currently we just use cargo vendor-filterer to make the vendor directory, and then tar and zip the resulting directories in shared code.
See https://crates.io/crates/cargo-vendor-filterer .
This would mean that the cargo vendor-filterer path is more separate from the regular vendor path in the release script. Currently we just use cargo vendor-filterer to make the vendor directory, and then tar and zip the resulting directories in shared code.