WolfStack v25.25.1
v25.25.1: a container on two Docker networks is reachable on its WolfNet IP again, and a VIP whose nat rules were wiped is rebuilt instead of answering only ping
klas's "ping works, curl does not, only changing the IP fixes it": the
container-WolfNet plumbing read a multi-network container's IP and MAC
as one concatenated string, so its DNAT and ARP entry silently failed
every tick; restarts skipped the WolfNet re-plumb; the LXC steady-state
route repair never ran; and a WolfRun VIP with a wiped ruleset was never
rebuilt. All four paths now self-heal, and the container action
handlers no longer block the async runtime.
Reported-by: klas
Co-Authored-By: CodeWolf paul@wolf.uk.com
Co-Authored-By: IntelligentWolf Ltd paul@wolf.uk.com
Claude-Session: https://claude.ai/code/session_01QCyHVCw4cGaTkfj1DRfCVW
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.