ci: rename release artifacts to target-triple shape (home#212) #27
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_db!27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_mik_home212_db"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Per home#212.
build-linux.yamlmatrixartifactfields renamed:linux-amd64→x86_64-unknown-linux-musllinux-arm64→aarch64-unknown-linux-gnu(honest gnu — workflow target was already gnu)All 6 existing v0.3.2 assets renamed via Forgejo asset-PATCH API in lockstep.
Consumer-side
service_db.nuupdated in lockstep on hero_skillsdevelopment_mik_home212_consumerbranch (suffix flipped from defaultlinux-amd64to explicitx86_64-unknown-linux-musl).Before: hero_db{,_server,_ui}-{linux-amd64,linux-arm64} After: hero_db{,_server,_ui}-{x86_64-unknown-linux-musl,aarch64-unknown-linux-gnu} The arm64 build target is gnu (not musl) per the existing matrix.target — the rename makes the asset name honestly reflect that. Existing v0.3.2 assets renamed via Forgejo asset-PATCH API in lockstep. Refs lhumina_code/home#212 Signed-off-by: mik-tf