Skip to content

ci: consolidate release build matrix with platform scripts and musl static binary#18

Open
aek676 wants to merge 3 commits into
xscriptor:mainfrom
aek676:main
Open

ci: consolidate release build matrix with platform scripts and musl static binary#18
aek676 wants to merge 3 commits into
xscriptor:mainfrom
aek676:main

Conversation

@aek676

@aek676 aek676 commented Jun 16, 2026

Copy link
Copy Markdown

Refactor the release workflow to use a single build matrix, making the
code more readable and maintainable. Platform-specific logic has been
extracted into dedicated setup/package scripts.

Changes:

  • Replace 5 separate build jobs with a single matrix (linux-x86_64, windows, macos-arm64)
  • Build Linux with x86_64-unknown-linux-musl target → one static binary that works on Debian, Fedora, and Arch (no more per-distro .deb/.rpm/.pkg.tar.zst)
  • Remove Fedora/Arch container builds in favor of the musl binary
image

aek676 added 3 commits June 16, 2026 00:51
Consolidate per-platform release jobs into a single matrix-based build
job. Add platform-specific setup and packaging scripts under
.github/scripts for linux-ubuntu, linux-fedora, linux-arch, macos
(x86_64 & arm64), and windows.

Use a unified build step and invoke a packaging script per matrix
target; artifacts are uploaded as asset-<target>. Update publish-release
to depend on the consolidated build job and to download and sign the
generated assets before creating the release.
ci: matrix realease for each SO build
@xscriptor

Copy link
Copy Markdown
Owner

Thanks for the PR. The matrix refactor is a good direction and I'd be happy to keep the musl static binary as an additional portable option. However, I can't drop the per-distro packages (.deb/.rpm/.pkg.tar.zst) because this application is being prepared for deep system integration through distro-specific channels, namely AUR and pacman. A generic tarball doesn't fit that distribution model long-term.
Could you adjust the PR to add the musl binary alongside the existing packaging rather than replacing it? Happy to help with the specifics.

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