You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
release: musl static build + publish to 5 codenames
Two coupled changes:
* Build the four release binaries with `--target
x86_64-unknown-linux-musl`. Static linking removes the glibc
floor entirely, so one .deb runs on bullseye (glibc 2.31) through
noble (2.39) without "version GLIBC_X.Y not found" surprises.
Possible because all four crates already use rustls (no OpenSSL
linkage to break under musl).
* Loop the upload across `bullseye focal jammy noble bookworm`.
Same .deb gets registered under each codename in
`packages.o1test.net`; deb-s3 happily handles the repeated
upload, and the underlying object in S3 is identical (just
referenced from five Packages indices).
To keep build-deb.sh from caring whether the binaries live under
`target/release/` or `target/<triple>/release/`, it now respects an
optional CARGO_TARGET env var that selects the subdir. Default
behaviour (no env var) is unchanged, so the package workflow keeps
working as-is — only release.yml opts into the musl path.
Release-notes body updated: the install snippet now leads with
"replace <CODENAME> with one of: bullseye focal jammy noble bookworm"
instead of pinning bookworm, and explicitly mentions the build is
musl-static so users understand why one .deb works everywhere.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments