Conversation
wpfleger96
approved these changes
Jul 10, 2026
`just staging` hardcoded `cp target/release/buzz`, which fails whenever CARGO_TARGET_DIR (or a cargo config `build.target-dir`) relocates build output away from ./target: the release build finishes fine, but the sidecar copy then can't find the binary. The package list was already correct — buzz-cli provides the `buzz` bin — only the artifact path was wrong. Resolve the effective target directory via `cargo metadata` before copying. Stock setups still resolve to ./target, so behavior there is unchanged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Matt Toohey <contact@matttoohey.com>
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
2 participants
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
The
just stagingrecipe copied the CLI sidecar binary from a hardcodedtarget/release/buzzpath. On machines where cargo's target directory is redirected (e.g. viaCARGO_TARGET_DIRor abuild.target-dirconfig), that path doesn't exist and the copy fails.This resolves the actual target directory via
cargo metadata --format-version 1 --no-depsand copies the builtbuzzbinary from<target_directory>/release/buzzinstead.Test plan
just stagingon a machine with a redirected cargo target dir; the sidecar stub is now replaced with the real CLI binary andtauri devpicks it up.🤖 Generated with Claude Code