Kalisto/ documentation source (permission required) ↗
On this page

#Binary releases and verification

Source is hosted in the GitHub repository. The download selector offers development candidates, not a stable release. The current candidate version is 0.0.0-ci.4476+g015c15f4bb23, from source revision 015c15f4bb23249196bf7f9e63e852b800da6a16. No tag or stable release is asserted or authorized by these guides.

The workflow is configured for macOS amd64/arm64 and static Linux amd64/arm64 with SHA-256 checksums. All four targets must build before tagged publication. Compilation/smoke checks do not prove backend runtime parity on every target; native Firecracker evidence currently applies to Fedora 44 x86_64.

#Download packages

For a successful tagged publication, the inventory is four archives and SHA256SUMS:

Package Rust target Build/smoke boundary
kalisto-TAG-macos-arm64.tar.gz aarch64-apple-darwin macOS runner; native --version
kalisto-TAG-macos-amd64.tar.gz x86_64-apple-darwin Cross-compiled on macOS arm64; Mach-O architecture verified
kalisto-TAG-linux-amd64.tar.gz x86_64-unknown-linux-musl Linux runner; native --version
kalisto-TAG-linux-arm64.tar.gz aarch64-unknown-linux-musl Linux cross-build; --version through user-mode QEMU

TAG includes v, for example v0.1.0—an example, not an available release. amd64 means x86_64; arm64 means aarch64. Each archive contains kalisto (mode 0755) and BUILD-INFO.json with tag, embedded version, full source commit and target. Candidate filenames/metadata identify their development build instead; use the selector's actual package rather than constructing a release URL.

Archive timestamps/ownership are normalized, not a guarantee of bit-for-bit reproducibility across compiler/SDK installations. Linux executables are static musl: native users need neither QEMU nor a matching glibc. QEMU is a CI cross-architecture smoke tool, not a native runtime prerequisite. macOS binaries are unsigned and not notarized. Intel output is architecture-checked, not runtime-tested on Intel hardware; CI never installs Rosetta automatically.

Verify downloads before installation:

sha256sum -c SHA256SUMS
# macOS alternative:
shasum -a 256 -c SHA256SUMS

Download all archives to check the whole checksum list, or select the matching line for your one downloaded archive. Checksums detect corruption, not an independently authenticated publisher signature; trust the configured source. Inspect embedded source/target metadata and never silently replace an existing installed binary.

#Pipeline and publication safety

Release workflow uses locked dependencies and Rust 1.89.0. Tests, Clippy, formatting and release-tool regression checks gate all four builds.

  • PR/manual workflow_dispatch builds upload candidates and verify the combined four-target inventory. They never create a release.
  • Pushed SemVer tags vMAJOR.MINOR.PATCH, optionally with prerelease/build suffixes, trigger configured publication. Invalid v* tags fail. No server/repository is hardcoded.
  • The publisher verifies inventory, embedded metadata, architecture and exact tag/commit provenance.
  • After all builds pass it creates a Forgejo draft, uploads four archives/checksums, downloads and verifies hashes, rechecks tag immutability, then makes the complete release visible.
  • Failure leaves any created release draft, never a partial public release.
  • Published releases are never overwritten. Matching partial draft uploads may resume; differing assets, unexpected attachments, moved tags or different source stop for inspection without deleting user assets.
  • macOS checkout/toolchain/cache/target/temp output uses configured mounted external storage. Missing mounts fail before checkout/build; no internal-disk fallback. Native jobs have unique workspaces/temp/cluster state, while Cargo targets and immutable prepared assets retain external shared caches. Cleanup removes only owned workspaces, preserving shared caches/unrelated jobs.
  • Release compilation remaps checkout, Cargo/rustup cache and home paths to neutral prefixes in all binaries while preserving configured compiler flags.
  • Artifact actions are pinned to verified Forgejo-compatible commits. Tokens never enter logs/archives; credential-bearing asset requests never redirect to another origin.

#CI configuration

Set Forgejo repository Actions variables out of band. Git contains no private defaults; do not check actual host paths/private image names into workflows.

Variable Contract
KALISTO_LINUX_RUNNER Linux Docker-capable runner label.
KALISTO_CI_IMAGE Runner-accessible Debian-compatible image with Git, Bash, CA certificates, Python 3.9+, Rust/rustup, rustfmt, Clippy, sccache and Node.js for artifact actions. Builder installs Rust 1.89.0. ARM64 smoke needs qemu-aarch64; CI installs qemu-user with apt as root/passwordless sudo if absent.
KALISTO_CI_CONTAINER_OPTIONS Optional container options/host cache binds and destinations expected by image CARGO_HOME/sccache; empty means no host cache mounts.
KALISTO_MACOS_RUNNER Trusted native macOS runner with Xcode command-line tools, Git, Bash, Python 3.9+, Rust/rustup, Node.js and Homebrew Apple container. Never schedule untrusted/fork jobs on this shared host.
KALISTO_MACOS_VOLUME Absolute path to an already mounted external volume, not /.
KALISTO_MACOS_BUILD_ROOT Writable directory strictly beneath that volume on the same filesystem. Owns workspaces and shared cargo-home, release-rustup, sccache, apple-container-ci/target, apple-container-ci/artifacts and per-target release-target caches.

Native cargo, rustc, rustup must be on PATH; populate the normal CI toolchain under external release-rustup using RUSTUP_HOME="$KALISTO_MACOS_BUILD_ROOT/release-rustup" and CARGO_HOME="$KALISTO_MACOS_BUILD_ROOT/cargo-home". Do not copy personal credentials into shared caches.

The functional job enables KALISTO_LIVE_APPLE_CONTAINER_BOOT_BUDGET=1 and keeps the full sixty-second three-node assertion. It borrows a running Homebrew service or starts an installed unregistered service without replacing a daemon, installing a kernel, changing roots or stopping it. Per-job XDG_DATA_HOME/XDG_CONFIG_HOME isolate ownership; cleanup never targets user cluster state. See native acceptance.

Forgejo supplies GITHUB_SERVER_URL (HTTPS origin), GITHUB_REPOSITORY (owner/name), GITHUB_TOKEN, GITHUB_EVENT_NAME, GITHUB_REF, GITHUB_SHA, GITHUB_RUN_ID, GITHUB_ENV. Publication needs token permissions to read tags and read/write releases/attachments in that repository. No other destination is inferred. HTTPS downloads/redirects remain limited to the configured origin. Candidates need the instance's artifact service.

GitLab configuration uses public Rust/Ubuntu/Debian images and standard GitLab variables, without private runner labels/registry dependencies. Runners need declared image architectures and existing privileged image-building tools. Put runner builds_dir and cache storage on the external volume so project-local output/job scratch stay there.

CI validation commands:

python3 -m unittest discover -s scripts/release -p 'test_*.py' -v
cargo fmt --all --check
cargo clippy --locked --all-targets --all-features -- -D warnings
cargo test --locked -- --test-threads=1

These commands document CI, not permission to run local validation. A manual workflow builds/verifies all four candidates without publishing. Native functional checks run only on configured authorized CI and create/destroy a real owned cluster, not a mock. Native archive restore remains separately unproven.

#Explicitly authorized tagged publication

Choose a reviewed commit with green CI and a new version. Illustrative commands only; no release/tag creation is authorized by this documentation:

git tag -s v0.1.0 COMMIT
git push origin v0.1.0

origin must point to the configured Forgejo repository. The pipeline resolves lightweight/annotated tags, checks out the exact commit and embeds the tag version including prerelease suffixes. Prerelease suffixes create prereleases. Never force-move release tags; choose a new version. Reruns against an already published release stop safely without changing it. The workflow never creates version tags; opening a PR or running a manual candidate build never creates a tag/release.