Skip to content

Restow 0.4.6

Choose a tag to compare

@github-actions github-actions released this 23 Oct 17:34
· 54 commits to main since this release

Restow 0.4.6. Released 2026-10-23, channel beta.

Beta release. Run it alongside your existing backups, not as your only one, until
you have verified restores against your own data.

Summary

Restow 0.4.6 fixes restoring Proxmox VE containers, which failed on current Proxmox VE for
every restore and every boot test of a container, and stops a new backup chain from being
flagged as a ransomware attack. Removed machines keep their backups browsable until they are
deleted, a requested restore check says it is queued until its result is in, and error texts
open in a card that can be copied. No database migration.

Breaking Changes

None. The integration API contract stays at 1.6.0.

Added

  • Removed machines (#65): until their backups are deleted, the page of a removed machine offers
    their restore (and nothing else), and the restore points, browsing, the ZIP download and the
    repository key keep working for them, audited as before. The list of removed machines links
    "Restore files". Restoring onto the machine and every other action stay refused (404); once
    the backups are deleted the machine is gone for every reader (docs/AGENT.md).

Changed

  • Error texts behind a badge or a cut-off line (the boot test, the restore check of a VM or
    container on its page and in the recovery readiness table) open on hover or keyboard focus in
    a card with the whole text, selectable and with a Copy button, instead of a browser tooltip.
  • A boot test that did not boot shows the node's message under its badge, on the guest's page
    and in the recovery readiness table.
  • "Check now" of a VM or container: the row says "Check queued" under the last check, and the
    guest's page above the earlier result, until the result is in; both refresh every few seconds
    meanwhile.
  • Dependencies: happy-dom 21.0.4 (tests of the web interface only; Dependabot #78).

Fixed

  • Proxmox VE: restoring a container from Restow failed with Can't use string ("restow") as a HASH ref on current Proxmox VE, which passes the storage ID to the backup provider's
    container restore before the info hash. Boot tests of containers ("Did not boot") and
    "Restore as a new guest" of containers were affected; VMs were not. The plugin of restow-pve
    accepts both forms; it is installed with the restow-pve update, which reloads the PVE daemons.
  • Ransomware detection: the first backup of a container's new backup chain (its repository was
    missing, or reset) was judged against the old chain and flagged as suspicious, since every
    file is new in an empty repository. The baseline now begins with the newest chain. A restore
    point flagged that way before the update stays flagged; mark it as a false alarm.
  • The first backup of a container's new backup chain is called "First backup", not
    "Incremental".

Security

None.

Upgrade Notes

  • No database migration and no new setting.
  • Update restow-pve on every Proxmox VE node (the server offers it after its own update; nodes
    update themselves when idle) before relying on container restores or boot tests. Until then,
    container restores keep failing as before; VMs are not affected.
  • Container restore points that read "Did not boot" or a failed restore check from before
    0.4.3: run "Boot test now" or "Check now" once the node is updated.

Known Issues

  • The known issues of 0.4.5 still apply.

Verification

Before the tag, on the release branch (0.4.5 plus the 0.4.6 fixes): lint and typecheck of all
workspaces, the unit and Postgres suites of every package on Postgres 16 (with the Postgres
guard), restic-backed tests with restic 0.19, the web DOM tests, the Perl tests of the Proxmox VE
plugin (the container restore with and without the storage ID) and the third-party notices.
The release smoke runs in the release pipeline; the container restore fix was not run against
a real Proxmox VE node before the tag.

Release pipeline, 2026-10-23:

Check Result Duration
1. Install: images, compose up, migrations (new install and upgrade) PASS 81s
2. Health endpoints, worker and scheduler registered PASS 0s
3. Passkey sign-in E2E with a virtual authenticator, tenant creation, i18n de/en PASS 2m 06s
4. Microsoft 365 backup and restore against the dev tenant SKIPPED 0s
5. IMAP backup and restore against Dovecot, hash comparison PASS 8s
6. Journal receipt, chain verification, export PASS 3s
7. Standalone restore with restow-restore from the storage of check 5 PASS 24s
8. Storage targets: S3 (Garage), local path, mounted directory PASS 21s
9. Image scan (Trivy) and dependency audit (pnpm audit) PASS 18s
10. Endpoint backup: the agent enrolls, backs up a folder, restores it PASS 11s
11. Mail import (folder and upload) and export (EML ZIP, MBOX), compared by hash PASS 10s
12. File share backup against Samba: back up, browse, ZIP, restore with permissions, copy job PASS 2m 14s
13. Archive capture: IMAP sync with IDLE and backfill, forwarded copies, dedupe, chain PASS 2m 12s

12 of 13 checks passed in full, 0 partly, 1 skipped, 0 failed. The full report, including the reason for every skipped or partial check, is attached to the release as smoke-report.md.

The Community images were smoke-tested on their own (smoke-report-community.md, smoke-report-community-arm64.md): amd64 PASS with gaps: 9 of 13 checks passed in full, 0 partly, 4 skipped (see the reasons below); arm64 PASS with gaps: 9 of 13 checks passed in full, 0 partly, 4 skipped (see the reasons below).

Images

Two builds of the same release. The full build is the Apache-2.0 core plus the Business and Service Provider modules (Restow Enterprise License), which stay locked until a license key is installed. The Community build is the Apache-2.0 core alone.

ghcr.io/restow-backup/restow:0.4.6
ghcr.io/restow-backup/restow-web:0.4.6
ghcr.io/restow-backup/restow-community:0.4.6
ghcr.io/restow-backup/restow-web-community:0.4.6

The digests of the multi-arch manifests (the opt-in updater verifies the pulled images against the two lines of its build):

restow: sha256:f8f434dccc12ab25cabe2f2c497d36bba5d62ba2283a76ea08c320e0b679f91e
restow-web: sha256:1199a6bfe5596080c7e3648ae63a9c166065429278d166fca7cabadcb11dfa5e
restow-community: sha256:7c6ebe881d8cc68c1d3c409742d8adbf64d8d2c3d90b62783b874db28c475b03
restow-web-community: sha256:e0422584558c96796e5404a79d60595cff576b5ba8a8d6a63aa7771b39879f2b

The release date the images carry (RESTOW_RELEASED_AT, the commit date of the tag). Licence keys with an update period cover the releases made up to its end; the updater reads this line to offer only those (docs/LICENSING.md):

released: 2026-10-23T16:00:22Z

All four images are multi-arch (linux/amd64, linux/arm64), signed with cosign (keyless) and carry an SPDX SBOM as attestation. Verify any of them with:

cosign verify ghcr.io/restow-backup/restow:0.4.6 \
  --certificate-identity-regexp '^https://github.com/restow-backup/restow/\.github/workflows/release\.yml@refs/tags/v' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com
cosign verify ghcr.io/restow-backup/restow-web:0.4.6 \
  --certificate-identity-regexp '^https://github.com/restow-backup/restow/\.github/workflows/release\.yml@refs/tags/v' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com
cosign verify ghcr.io/restow-backup/restow-community:0.4.6 \
  --certificate-identity-regexp '^https://github.com/restow-backup/restow/\.github/workflows/release\.yml@refs/tags/v' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com
cosign verify ghcr.io/restow-backup/restow-web-community:0.4.6 \
  --certificate-identity-regexp '^https://github.com/restow-backup/restow/\.github/workflows/release\.yml@refs/tags/v' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

The public demo's own images, ghcr.io/restow-backup/restow-demo-seed:0.4.6 and ghcr.io/restow-backup/restow-demo-dovecot:0.4.6 (deploy/demo), carry the same tags, signatures and SBOMs; they are no part of an installation.

docker-compose.yml and env.example are the release stack (deploy/release/); install.sh installs it on a dedicated Linux VM (README.md, "Install with the script"; install.sh.sha256 for sha256sum -c after the download); restow-agent-THIRD_PARTY_NOTICES.txt holds the licenses of the agent binaries and of the restic they run; SHA256SUMS lists every file of this release and is signed (SHA256SUMS.sigstore.json).