ci: rename release artifacts to target-triple shape (home#212, honest gnu) #20
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_shrimp!20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_mik_home212_shrimp"
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.
Not in the original home#212 migration table — added during the rename arc audit. Workflow runs
cargo build --releasewithout--target, producing host-defaultx86_64-unknown-linux-gnubinaries insideghcr.io/despiegk/builder:latest. Oldlinux-amd64was concealing the libc.build-linux.yamlSUFFIX="linux-amd64"→SUFFIX="x86_64-unknown-linux-gnu".4 existing v2.0.0 assets renamed via Forgejo asset-PATCH API in lockstep (the workflow currently builds 3 of those 4 —
hero_shrimp_cliexists from a prior workflow shape and was renamed for backward-compat with external consumers).Consumer-side
service_shrimp.nuupdated in lockstep on hero_skillsdevelopment_mik_home212_consumerbranch.Honest gnu rename — workflow runs cargo build --release without --target, producing host-default x86_64-unknown-linux-gnu binaries. Existing linux-amd64 suffix was concealing the libc. Before: hero_shrimp{,_server,_ui}-linux-amd64 After: hero_shrimp{,_server,_ui}-x86_64-unknown-linux-gnu Existing v2.0.0 assets (including a hero_shrimp_cli that's no longer in the workflow's binary list — kept and renamed for backward compat with external consumers) renamed via Forgejo asset-PATCH API in lockstep. Refs lhumina_code/home#212 Signed-off-by: mik-tf