WolfStack v25.24.0
v25.24.0: warm-standby fixes from a live Proxmox failover, plus secrets export and deploy-stack-to-node
Nested storage mounts come up parents-first and never over a live child, the
service unit survives a missing /opt/wolfstack, compose reports the ${KEY}s it
resolved blank, and the daemon says which stacks have never been started on
this host. New: passphrase-sealed export/import of the Secrets Manager, and a
one-click deploy of a compose stack — with its referenced secrets — to another
WolfStack node.
Co-Authored-By: CodeWolf paul@wolf.uk.com
Co-Authored-By: IntelligentWolf Ltd paul@wolf.uk.com
Claude-Session: https://claude.ai/code/session_01F6WgFfZnkidT9DuzaYFxeK
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/intelligentwolf/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 intelligentwolf/WolfStack
Verify the SHA-256 checksum:
sha256sum -c SHA256SUMS
Artifacts
wolfstack-x86_64/wolfstack-aarch64/wolfstack-armv7— static musl binaries (Linux x86_64, ARM64 / Raspberry Pi 4+, and 32-bit ARM).wolfstack-<arch>.cosign.bundle— cosign signature bundle (cert + signature + Rekor entry).SHA256SUMS— checksums for both binaries.
For per-version history see CHANGELOG.md.