-
Notifications
You must be signed in to change notification settings - Fork 12
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
Fix vendor Rust: limit to manifests from backend #532
Conversation
I need to verify the changes with cryptography 42, 43, and 44. |
Looks like a ci failure
|
a0c23b1
to
eec7e9c
Compare
I have successfully built |
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 looks OK to me, with a couple of small nits.
@pnasrat , have you had a chance to try it out to see if it resolves your issue, too?
90a8b75
to
53daee5
Compare
Fromager was vendoring crates from all `Cargo.toml` files in a project. This approach is causing issues for projects that have cargo files in tests and example directories. The `vendor_rust()` function now only vendors crates from `Cargo.toml` in the project's root directory and additional cargo files listed in `tools.maturin` or `tools.setuptools-rust` entries. Fixes: python-wheel-build#529 Signed-off-by: Christian Heimes <[email protected]>
53daee5
to
28c0d57
Compare
it'd be great to get this merged - its been working for me on the PR checked out |
Excellent, I was just waiting to hear back from you and then it fell off of the top of my todo list. |
@Mergifyio refresh |
✅ Pull request refreshed |
Released in 0.38.0 |
Fromager was vendoring crates from all
Cargo.toml
files in a project. This approach is causing issues for projects that have cargo files in tests and example directories.The
vendor_rust()
function now only vendors crates fromCargo.toml
in the project's root directory and additional cargo files listed intools.maturin
ortools.setuptools-rust
entries.Fixes: #529