Skip to content

Fix release asset build path (Fixes #1) - #2

Merged
p0dalirius merged 1 commit into
mainfrom
bugfix-release-asset-build-path
Oct 9, 2026
Merged

p0dalirius merged 1 commit into
mainfrom
bugfix-release-asset-build-path

Conversation

@p0dalirius

Copy link
Copy Markdown
Collaborator

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

  • Runtime: go test ./... passes.
  • Runtime: executed the corrected Linux/amd64 build command and the unchanged staging copy; ./release/DescribeKeyCredentialLink-linux-amd64 was present afterward.
  • Static: actionlint v1.7.7 passes with only the repository pre-existing legacy-action version diagnostics excluded.
  • Static: git diff --check passes.

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

  • Files changed: .github/workflows/release.yaml
  • Submodule pointer updated: no
  • Behavioral changes outside the bug fix: none

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.

@p0dalirius
p0dalirius merged commit cd62f7b into main Oct 9, 2026
8 checks passed
@p0dalirius
p0dalirius deleted the bugfix-release-asset-build-path branch October 9, 2026 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Correct mismatched release artifact paths

1 participant