WolfStack v25.28.0
v25.28.0: a Compose stack can be force-recreated from the Compose page
Up recreates only the containers whose definition differs from the
compose file, so a container that has drifted at runtime — a lost
network attachment, a half-applied restart, state compose cannot see —
is left exactly as it is, and Restart reuses the same container. klas
asked for the third option: rebuild every container in the stack from
the compose file whether compose thinks it changed or not.
The Compose page gains a Recreate button, backed by
POST /api/compose/stacks/{name}/recreate, which runs
docker compose up -d --force-recreate --remove-orphans through the
same command builder as Up — the two can only ever differ by that flag
— and returns the same report: which containers came back and which
${KEY}s compose substituted blank. Volumes are kept; the containers are
new.
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.