fix(plt-147): remove broken same-registry zerocopy patch - #34
Merged
Conversation
[patch.crates-io] cannot point to the same registry source. The Windows AVX-512 zerocopy fix is handled via RUSTFLAGS set in the GitHub Actions workflow via GITHUB_ENV.
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
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
[patch.crates-io] zerocopy = { version = "=0.7.35" }which is invalid: Cargo requires patches to point to a different source (git/path), not the same crates.io registry.patch for zerocopy points to the same source, but patches must point to different sourcesGITHUB_ENVin the release workflow.Root cause
[patch.crates-io]requires the replacement to come from a different source (e.g.git = "..."orpath = "..."). Pointing to another crates.io version is not supported.PLT-147