Skip to content

fix(ci): rename release binaries to avoid asset name collisions#123

Merged
odesenfans merged 1 commit into
mainfrom
od/fix-release-asset-names
Mar 23, 2026
Merged

fix(ci): rename release binaries to avoid asset name collisions#123
odesenfans merged 1 commit into
mainfrom
od/fix-release-asset-names

Conversation

@odesenfans
Copy link
Copy Markdown
Contributor

The #label in gh release upload "file#label" only sets the display name — the actual asset filename is the uploaded file's name. All non-Windows matrix jobs produced a binary called aleph, so --clobber made them overwrite each other (only one survived).

Fix by copying the binary to the unique asset_name before uploading, and revert the separate upload-release-assets job from 398e048 since it is no longer needed.

The #label in `gh release upload "file#label"` only sets the display
name — the actual asset filename is the uploaded file's name. All
non-Windows matrix jobs produced a binary called `aleph`, so --clobber
made them overwrite each other (only one survived).

Fix by copying the binary to the unique asset_name before uploading,
and revert the separate upload-release-assets job from 398e048 since
it is no longer needed.
Copy link
Copy Markdown

@foxpatch-aleph foxpatch-aleph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR correctly fixes the asset name collision issue by renaming binaries to unique names before upload. The solution is cleaner and more efficient than the previous approach with separate artifact upload/download jobs. The added permissions are necessary, and dependency updates are correct. No bugs or security issues found.

@odesenfans odesenfans merged commit 545e29f into main Mar 23, 2026
9 checks passed
@odesenfans odesenfans deleted the od/fix-release-asset-names branch March 23, 2026 21:46
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.

2 participants