Skip to content

WolfStack v25.25.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Sep 08:26
· 17 commits to master since this release
v25.25.3
9d84350

v25.25.3: a WolfNet IP can no longer be claimed by two owners at once, and one that is gets named in the inbox

klas's containers kept losing their service on their WolfNet IP —
ping answered, curl did not, the published host:port kept working, and
only changing the IP fixed it. Every one of those is what a second
owner of the address produces. WolfStack built its cluster route map
from the addresses of stopped workloads as well as running ones, so an
IP held stopped on one node and running on another had two claimants
and every node re-picked the winner on each poll. Routing now counts
only running workloads, while allocation still reserves the stopped
ones cluster-wide, and it also stops handing out addresses WolfNet
already delivers to a peer — including the roaming and PEX-learned
peers the config file never lists. A stopped container keeps its NAT
rules through a restart and loses them only when another container
actually takes the address they point at. A conflict that genuinely
needs an operator now appears in the inbox with the address and both
holders named.

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_01FhuukEg1oyTLpRXQJqpGxA

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.

Assets 9
Loading