Open
Description
openedon Aug 26, 2023
Cargo's CI should verify that its packages can build before being published.
Cargo is published to crates.io with --no-verify
, in part because the publishing system isn't prepared for doing verification. However, that would also only verify for one platform.
Ever since switching cargo to a workspace, we've had problems with workspace feature unification causing problems that aren't discovered until after cargo is published (#12017, #12565). Our CI can't detect these issues because all tests are done with feature unification.
Unfortunately cargo package
can't be used due to version bumps of local dependencies (#9260).
I'm not sure if or how this could be fixed without changes to cargo itself.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
Area: cargo's testsArea: cargo's testsStatus: Needs someone to work further on the design for the feature or fix. NOT YET accepted.Status: Needs someone to work further on the design for the feature or fix. NOT YET accepted.