dist-workspace.toml

[workspace]
# The kittylitter wrapper crate at services/kittylitter re-exports the
# alleycat daemon under a kittylitter-branded name. cargo-dist runs against
# that workspace and produces kittylitter-* artifacts hosted on this repo's
# GitHub Releases.
members = ["cargo:services/kittylitter"]

[dist]
cargo-dist-version = "0.31.0"
ci = "github"
# npm is the only distribution channel for now. Homebrew, shell installer,
# powershell installer, and MSI can be re-enabled later by adding them back
# to this list (and to publish-jobs for the registry-publishing ones).
installers = ["npm"]
targets = ["aarch64-apple-darwin", "aarch64-unknown-linux-gnu", "x86_64-apple-darwin", "x86_64-pc-windows-msvc", "x86_64-unknown-linux-gnu"]
# Keep Windows on the native x64 GitHub runner for now. The aarch64 Windows
# target still needs cargo-xwin/ring cross-compilation coverage before it can
# be added safely.
install-path = "CARGO_HOME"
hosting = "github"
install-updater = false
# Code-sign macOS binaries with the Developer ID Application cert in
# `dnakov/litter`'s repo secrets. Even though npm doesn't trigger Gatekeeper,
# signing gives the binary a stable identity for TCC (Local Network) and
# launchd. Required secrets (cargo-dist 0.31 names):
#   CODESIGN_CERTIFICATE          base64 of MAC_DEVELOPER_ID_CERT_P12_B64
#   CODESIGN_CERTIFICATE_PASSWORD same as MAC_DEVELOPER_ID_CERT_PASSWORD
#   CODESIGN_IDENTITY             "Developer ID Application: <Name> (<TEAM>)"
macos-sign = true
# Inject sccache (Cloudflare R2 backend, same key/secret as the mobile
# lanes) into the build-local-artifacts job so kittylitter releases
# don't recompile iroh/ring/reqwest from scratch on every bump. Path is
# resolved relative to .github/workflows/, so `../` escapes to .github/
# (we don't want this fragment under workflows/ because GitHub would
# otherwise treat it as a standalone workflow). Requires the
# SCCACHE_R2_* + AWS_* repo secrets that other lanes already use.
github-build-setup = "../dist-build-setup.yml"
# Run the npm publish job on tagged releases. Requires NPM_TOKEN.
publish-jobs = ["npm"]
# Add a `workflow_dispatch` trigger to release.yml so the auto-release
# wrapper workflow can invoke it on demand (without us pushing a tag
# manually). cargo-dist still creates the tag internally as part of the
# release; we never run `git tag` ourselves.
dispatch-releases = true
# Open a PR with the generated workflow on changes rather than overwriting silently.
pr-run-mode = "plan"