WolfStack v25.1.35

v25.1.35: LXC / app-store containers request the host's arch (arm64), not a hardcoded amd64

On arm64 hosts (OrangePi 5 / RK3588 etc.) LXC templates and container configs
hardcoded architecture "amd64", so an ARM node pulled a wrong-arch, unbootable
rootfs — LXC deploys and app-store LXC apps failed.

New containers::host_container_arch() maps the running arch to Debian/LXC
image naming (x86_64→amd64, aarch64→arm64, arm→armhf). Applied to: the LXC
template fallback lists + Proxmox-template parse default, both ContainerExportMeta
defaults, the lxc.arch config line, wolfrun's LXC-deploy default + serde
default_arch(), and all 26 app-store LxcTarget definitions.

On x86_64 the helper returns "amd64", so existing hosts are byte-identical — only
ARM hosts change. Does not touch the login-loop / node-offline / autofix reports
(separate, need node logs).

---

Verifying this release

Each binary is signed via cosign keyless OIDC (no key distribution — signing identity is the GitHub Actions workflow itself, anchored to the Sigstore Fulcio CA and the Rekor transparency log) and ships with a SLSA build provenance attestation.

Verify the cosign signature:

cosign verify-blob \
  --bundle wolfstack-x86_64.cosign.bundle \
  --certificate-identity-regexp 'https://github.com/wolfsoftwaresystemsltd/WolfStack/\.github/workflows/release\.yml@.*' \
  --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
  wolfstack-x86_64

Verify the build provenance:

gh attestation verify wolfstack-x86_64 --repo wolfsoftwaresystemsltd/WolfStack

Verify the SHA-256 checksum:

sha256sum -c SHA256SUMS

Artifacts

• wolfstack-x86_64 / wolfstack-aarch64 — static musl binaries (Linux x86_64 and ARM64 / Raspberry Pi 4+).
• wolfstack-<arch>.cosign.bundle — cosign signature bundle (cert + signature + Rekor entry).
• SHA256SUMS — checksums for both binaries.

For per-version history see CHANGELOG.md.