Publish versioned binary releases on Forgejo package registry #35
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_proc#35
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Summary
Set up automated binary releases for hero_proc on the Forgejo package registry so downstream consumers (e.g. znzfreezone_vdc node installer) can reliably fetch pinned or latest versions.
Current State
Binaries are published manually at:
Requested
v0.4.2)latestversion alias so consumers can fetch the newest buildhero_proc,hero_proc_server,hero_proc_uix86_64-unknown-linux-musl(static binary, no glibc dependency)Why
The ZNZ Free Zone node installer (
znzfreezone_node_installer) needs to download hero_proc binaries at build time or at node initialization. Having a stablelatestURL and versioned releases makes this reliable and reproducible.Related