[codex] Fix native SDK runtime crate packaging - #664
Merged
Conversation
i386
marked this pull request as ready for review
May 24, 2026 05:10
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.
Generated native SDK runtime crates now declare their own empty workspace, so
cargo packagetreats them as standalone crates even when they are emitted under the mesh-llm checkout.Root Cause
The release workflow writes generated runtime crates under
dist/native-sdk-crates/.... Because that path is inside the repository, Cargo found the parentCargo.tomlworkspace and failed with:The generated crates are publishable artifacts rather than workspace members, so the manifest template needs to opt out of the parent workspace.
Validation
bash -n scripts/package-native-sdk-crate.shgit diff --checkmeshllm-native-linux-x86_64-cpuartifact undertarget/native-sdk-crate-smoke/..., matching the CI condition where Cargo can see the parent workspace