Repository navigation
WolfStack v24.3.15
v24.3.15: restore dialog warns when the target name is already taken
Restoring under a name that already exists — e.g. an accidental
second restore of a container that restored fine, or a leftover
directory from an earlier failed restore — previously surfaced only
as a post-hoc error after the restore ran. Now the dialog flags it
up front.
- New GET /api/containers/lxc/{name}/exists — reports whether an LXC
container, or a leftover dir from a failed restore, already occupies
the name (checks /var/lib/lxc/ and /etc/pve/lxc/.conf).
The name is validated with is_safe_name before it touches a path. - Both restore dialogs (the Backups list and the PBS snapshot list)
now check the name field on open and as it is edited, showing an
inline warning when the name is taken and pointing the operator at
the Replace option.
The restore itself still refuses to clobber an existing target unless
Replace is ticked — this only surfaces the collision earlier. No
change to the v24.3.13 restore logic.
Co-Authored-By: CodeWolf paul@wolf.uk.com
Co-Authored-By: Wolf Software Systems 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/wolfsoftwaresystemsltd/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 wolfsoftwaresystemsltd/WolfStack
Verify the SHA-256 checksum:
sha256sum -c SHA256SUMS
Artifacts
wolfstack-x86_64/wolfstack-aarch64— static musl binaries (Linux x86_64 and ARM64 / Raspberry Pi 4+).wolfstack-<arch>.cosign.bundle— cosign signature bundle (cert + signature + Rekor entry).SHA256SUMS— checksums for both binaries.
For per-version history see CHANGELOG.md.