ci: rename release artifacts to target-triple shape (home#212) #61
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_aibroker!61
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_mik_home212_aibroker"
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.
Both tag-firing workflows updated:
release.yamlmatrix:linux-amd64-musl→x86_64-unknown-linux-muslbuild-linux.yamlmatrix:linux-amd64→x86_64-unknown-linux-musl,linux-arm64→aarch64-unknown-linux-gnu4 existing v0.1.1 assets (the musl-only ones from
release.yaml—build-linux.yaml's arm64 leg apparently doesn't currently publish) renamed via Forgejo asset-PATCH API in lockstep.Consumer-side
service_aibroker.nuupdated in lockstep on hero_skillsdevelopment_mik_home212_consumerbranch.Both release.yaml and build-linux.yaml updated: - release.yaml: linux-amd64-musl → x86_64-unknown-linux-musl - build-linux.yaml: linux-amd64 → x86_64-unknown-linux-musl linux-arm64 → aarch64-unknown-linux-gnu (Both workflows fire on tag push today; the linux-amd64 entry in build-linux.yaml is musl per its target, the linux-arm64 entry is gnu per its target — names now reflect that honestly.) Existing v0.1.1 assets renamed via Forgejo asset-PATCH API in lockstep (only the 4 musl assets exist today; build-linux.yaml's gnu/arm64 output is not currently published to v0.1.1). Refs lhumina_code/home#212 Signed-off-by: mik-tf