Merged
Conversation
PyPI rejected linux_aarch64 wheels because manylinux: auto on native ARM runners skips Docker, producing non-manylinux platform tags. Using explicit manylinux_2_28 forces Docker container usage, producing PyPI-compatible manylinux_2_28_* wheel tags.
Previous approach mounted parent at /parent and created symlinks, but Cargo resolves paths relative to actual workspace location. Now mounts sibling deps at their exact expected paths so Cargo's `../syft-crypto-core` resolves correctly inside Docker container.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/parentmount + symlinks (failed - Cargo resolves relative to actual workspace path)${{ github.workspace }}/../syft-crypto-coreso../syft-crypto-coreresolves correctlyTest plan