Building and publishing releases
scripts/release-build.sh <tag> <output-dir> stages a qualified release from a fresh checkout of the tag. It runs the static build and its release gates, then builds the cross targets in isolated trees with bounded concurrency. The measured budget is the minimum of eight, the available CPUs minus the one-minute load and two reserved CPUs (rounded down), and the available memory minus 1 GiB headroom divided by 5 GiB per target (rounded down). A zero budget refuses before any target starts; at least 6 GiB available memory is required. SIGIL_RELEASE_JOBS=1 requests serial builds; values through eight request a limit within that same printed budget. To deliberately exceed it, invoke the driver with an explicit jobs request and --force-jobs; it prints a warning and retains the hard cap of eight. Systems without resource probes use a budget of one with a warning. Target logs, caches, and work trees are retained in the build work directory.
The output contains the platform binaries and allocator sidecars, SHA256SUMS, BUILD-INFO, release-body.md, and compatibility JSON (latest.json and v<version>.json). The qualified static binary and sidecar stay private until every cross target succeeds; the pool then stages static and cross artifacts together. A failed cross target leaves the output empty and prevents aggregate release records from being generated. Every failed target is listed with its retained log path.
To qualify an untagged commit, set SIGIL_RELEASE_CANDIDATE_COMMIT to its full 40-character lowercase commit ID and SIGIL_RELEASE_SRC_REPO to a repository containing it. The positional version must still match package.sgl; this does not bump the version or create a tag. Candidate output is marked NOT-A-RELEASE and contains CANDIDATE-INFO and checksums instead of publication metadata. Build the final tagged tree again before publishing it.
For candidate qualification, retain the complete release build together: the executable and its allocator sidecar, sibling libraries and assets, and build/release/native/allocator-mimalloc.o, build/release/native/libsigil.a and build/release/native/libsigil-sqlite.a. The allocator gate consumes these native inputs as well as the CLI. Build them before running make test-release-suite or make test-allocators ALLOCATOR_TEST_CONFIG=release.
On Node 22.14.0 under an 8 GiB address-space cap, default WebAssembly trap handling failed to instantiate the allocator test module because it could not reserve memory. With NODE_OPTIONS=--disable-wasm-trap-handler, the identical module and the complete allocator gate passed under the same cap. Use that setting when qualifying in this bounded environment; this observation does not establish the behavior of every Node runtime.
test-shell invokes rg, so include ripgrep in the test environment. For example, run guix shell -m manifest.scm ripgrep -- make test-shell.
Publication uses the separate sigil-publish-release.sgl VERSION workflow, which starts in plan mode. It publishes qualified releases through the Sigil registry. scripts/release-publish.sh is a retained refusal for older commands; it exits 125 and names the current publication path.
Public binary URLs are:
https://pkg.usesigil.org/dl/v<version>/<artifact>https://pkg.usesigil.org/dl/latest/<artifact>
Release notes live at https://usesigil.org/releases/<version>/. Current sigil cli upgrade and sigil cli use verify the signed registry toolchain index and artifact bytes. Compatibility JSON remains available for older CLIs and points at the same registry-hosted binaries; it is not the current CLI's trust source. Generating these files does not update the metadata channels embedded in older clients. RELEASE_DOWNLOAD_BASE_URL and RELEASE_NOTES_BASE_URL configure the standalone compatibility generators.
Codeberg source Git mirrors, including codeberg:sigil/sigil dependencies, remain valid. The build and legacy CI no longer upload release binaries or development binaries to Codeberg releases.