-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
Uplift keys/dependencies to use more workspace inheritance #9293
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense to me -- thank you @Jefffrey
I wonder if there are any other tests we should run here to make sure it doesn't interfere with releases? @andygrove any thoughts?
Otherwise I think we should merge up from main and then this PR would be good to go.
@@ -51,6 +51,11 @@ rust-version = "1.72" | |||
version = "36.0.0" | |||
|
|||
[workspace.dependencies] | |||
# We turn off default-features for some dependencies here so the workspaces which inherit them can |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Thanks again @Jefffrey |
Which issue does this PR close?
Closes #.
Rationale for this change
Try use workspace inheritance more, for both regular package keys, and also dependencies
Note that due to rust-lang/cargo#11329 we need to specify
default-features = false
for the workspace dependency then override todefault-features = true
where we need, as the reverse does not work. If this isn't preferable we can revert back to the previous way of manually specifying these dependencies again without workspace inheritance.What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?