Repository navigation
Fix release asset build path (Fixes #1) - #2
Merged
Merged
Conversation
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.
Linked Issue
Closes #1
Root Cause
The release build step used a parent-relative output directory while the following staging step used a repository-relative input directory. The workflow therefore built the binary outside the directory searched by asset preparation.
Fix Description
Create the repository-local ./build directory and write the binary there. This makes the build output match the existing staging and upload paths while preserving the binary name and release filename format.
How Verified
Test Coverage
None: The defect is in release workflow path integration rather than application code. The exact corrected build and staging commands were executed end to end.
Scope of Change
Risk and Rollout
The change only relocates generated build output into the directory already consumed by release staging. Binary names, build flags, target matrices, and upload behavior are unchanged.