Skip to content

Set up Rust crates as members of a Cargo workspace #23051

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Set up Rust crates as members of a Cargo workspace #23051

wants to merge 1 commit into from

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Aug 7, 2025 •
edited
Loading

Set up Rust crates as members of a Cargo workspace

This has a few benefits:

  • We can do a full cargo publish --dry-run on all crates, which would not
    otherwise be possible since dependent crates would not be present yet on
    crates.io.
  • This makes manually testing the Cargo build easier, since you can have Bazel
    build all our crates into a single tar file.
  • This should make it easier to run our tests from rust/test/shared/ with
    Cargo in addition to Bazel.

@copybara-service copybara-service bot force-pushed the test_792352742 branch 4 times, most recently from 5be4bea to c1c0e8f Compare August 8, 2025 19:43
@acozzette @copybara-github
Set up Rust crates as members of a Cargo workspace
f8029f3 
This has a few benefits:
 - We can do a full `cargo publish --dry-run` on all crates, which would not
   otherwise be possible since dependent crates would not be present yet on
   crates.io.
 - This makes manually testing the Cargo build easier, since you can have Bazel
   build all our crates into a single tar file.
 - This should make it easier to run our tests from `rust/test/shared/` with
   Cargo in addition to Bazel.

PiperOrigin-RevId: 792352742
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@acozzette