ci(release): build linux, macos and windows binaries #1
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/release-binaries"
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
A
v*tag now also builds binary archives for Linux, macOS and Windows on the Linuxnixrunner and attaches them to the Forgejo release.x86_64-unknown-linux-musl.tar.gz, staticaarch64-unknown-linux-musl.tar.gz, staticx86_64-apple-darwin.tar.gz, ad-hoc signed (rcodesign)aarch64-apple-darwin.tar.gz, ad-hoc signed (rcodesign)x86_64-pc-windows-gnu.zipEach archive holds the binary, README, LICENSE, CHANGELOG, completions and (not on Windows) man pages, plus a
SHA256SUMS.Also:
flake.nix: newreleasedev shell. A newrust-overlayinput supplies a toolchain with the standard library for each target. The flake.lock change only adds that input.src/util.rs: on Windows,whichtries PATHEXT (claude.exe,codex.cmd),has_displayis true, and the browser opens viarundll32 url.dll,FileProtocolHandler.ci.yml: new stepcargo check --all-targets --target x86_64-pc-windows-gnu, with warnings denied. It caught an unused import intests/common, which is fixed.Evidence
cargo zigbuild --target x86_64-pc-windows-gnufails to link:unable to find dynamic system library "synchronization". Zig's MinGW lacks it, so Windows links with MinGW gcc instead.After:
nix develop .#release -c scripts/release-build.shproduces all 5 archives andSHA256SUMS. Run checks:quartz --versionprintsquartz 0.1.0.qemu-aarch64:quartz 0.1.0.quartz 0.1.0./usr/lib/libSystem,libiconvandlibcharset. It was not run on a real Mac.cargo fmt --check,cargo clippy --all-targets -D warnings,cargo testandnix flake checkall pass.Merge Danger
Door: two-way
Only workflows, a dev shell and small Windows-only code paths change. Revert to undo.
Blast Radius: releases
The asset upload has not run against Forgejo yet. It uses the same token that already creates releases. If it fails on the next tag, the release still exists and a re-run attaches only the missing files. CI gets slower on the first run while the runner fetches the rust-overlay toolchain and MinGW gcc.
🤖 Generated with Claude Code