WolfStack v25.26.0
v25.26.0: the inbox stops reporting a node that is long gone, and you choose which channels alerts go out on
klas had two complaints that were really the same shape: WolfStack
telling him things he could not act on. A finding about a node that
had left the cluster could never clear, because the pipeline only
clears what an analyzer looked at this tick and nothing was left to
look at. And notifications went to every channel that had credentials
plus email from a different settings page, so ntfy and SMTP together
meant two pages per event with no way to pick one.
Findings whose subject no longer exists now retire — immediately where
the analyzer can prove the resource is gone, otherwise after a
seven-day fuse — and are recorded as resource_gone, distinct from a
condition that genuinely cleared. Settings → Alerts → Notifications
gains "Deliver alerts to": tick the paths you want, and see what will
actually be delivered. Leaving everything ticked is exactly the old
behaviour, so existing installs are unchanged until you choose.
Reported-by: klas
Co-Authored-By: CodeWolf paul@wolf.uk.com
Co-Authored-By: IntelligentWolf Ltd paul@wolf.uk.com
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.