Build the packaged harness with stable Rust - #97
Merged
Conversation
Avoid nightly-only dependency behavior in the packaged harness while preserving nightly as the agent development toolchain.
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
Why
The agent image began failing on both amd64 and arm64 after the floating nightly channel advanced to Rust 1.100.0-nightly. The unchanged allocative 0.3.4 dependency enables overlapping never-type implementations only on nightly. Stable Rust omits that nightly-only code path. This unblocks #96 without coupling the toolchain repair to its workflow-host behavior.
Validation
The image validation workflow will rebuild and probe the packaged agent on both native amd64 and arm64 runners.