Skip to content

Restow 0.4.5

Choose a tag to compare

@github-actions github-actions released this 23 Oct 08:50
· 65 commits to main since this release

Restow 0.4.5. 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.5 prepares the licence for paid update periods: keys can carry an update period
and a series, the image knows its release date, and an installation is offered, told about and
allowed to install only the releases its Business or Service Provider key covers. Every key
issued so far is a beta licence and keeps covering every 0.x and 1.x release. Revoked machines
can be removed from Restow, with or without their backups; Microsoft 365 group calendars and
conversations are backed up as protected objects of their own (opt-in); both job lists can
start and stop every job and open a detail panel like VMs & containers. The public demo resets
from a saved template in about a minute. Three database migrations (Upgrade Notes).

Breaking Changes

None. The integration API contract moves to 1.6.0, additively: ObjectKind includes
group and the status reports lastSuccess.groups; clients that handle object kinds
exhaustively should accept the new value. Licence keys with the new optional members verify
only on 0.4.5 and later (ee/licensing/KEY-FORMAT.md).

Added

  • Licence keys carry update terms (docs/LICENSING.md). The key format restow-license-v1
    accepts the optional members series, updates_until and kid and ignores members it does
    not know, so keys the licence server issues later keep verifying; the six members of today
    stay required and keep their rules (mailbox_limit unchanged). Every key issued so far is a
    beta licence: it covers every 0.x and 1.x release. A key with updates_until covers every
    release made up to the end of that day (UTC). kid names the vendor signing key, for a
    rotation without breaking issued keys. The contract for the issuer, with examples, is
    ee/licensing/KEY-FORMAT.md.
  • The image carries its release date (RESTOW_RELEASED_AT, from the build argument
    RESTOW_CREATED, the commit date of the release tag); GET /api/v1/status reports it as
    releasedAt. Release notes publish the same date in a released: line next to the digests.
  • The update check marks releases the installed Business or Service Provider key does not
    cover, says so calmly on the Updates page (the installed version keeps working; the newest
    covered version installs as usual) and refuses to install or plan them (409
    urn:restow:problem:update-not-covered). The bell and the update.available alert rules
    announce only the newest covered release.
  • Started by hand, a release the installed Business or Service Provider key does not cover
    stops before its database migrations, with a log line naming the version, the end of the
    update period and the last covered release date; nothing needs to be restored to go back.
    With RESTOW_RUN_AS_COMMUNITY=1 it starts as Community instead (the modules stay off, no
    data is changed). Never for beta licences, development builds, installations without a key
    or the demo.
  • The licence page shows which updates the key includes ("all 1.x (beta license)" or the end
    of the update period) and, from 30 days before the end, a short notice on the same page.
    A new key of the same edition replaces the active one even while it is in force (a
    renewal); earlier keys stay in the history, and every installation or replacement is
    audited with the key's update terms and whether they cover the running version. A key that
    does not cover the running version is refused (outside_update_period).
  • Public demo, fast nightly reset (deploy/demo/README.md "Fast reset"): after a full seed
    deploy/demo/reset.sh saves a template (a pg_dump of the demo database, its roles and a tar
    of every volume the seed writes) keyed by the release, the image ids and .env, and restores
    it the following nights instead of seeding: the database is restored next to the running one
    and swapped in, so the demo is offline for about 15 to 25 seconds instead of many minutes. The
    restore moves every system time forward by the template's age (deploy/demo/seed/sql/ shift-time.sql), so the history still ends today and "last backup 12 minutes ago" stays true;
    the audit log, the mail archive and restic's own snapshot times keep their real times, sign-ins
    are removed. A template older than RESTOW_DEMO_TEMPLATE_MAX_AGE_DAYS (default 7), a new
    release, new images, a changed .env or a failed restore lead to a full seed. Two templates are
    kept, with a free-space check before saving (RESTOW_DEMO_TEMPLATE_* settings,
    RESTOW_DEMO_TEMPLATES=false switches it off).
  • Machines: a revoked machine can be removed from Restow (#65). "Remove from Restow" in its
    danger zone offers "Remove from the list, keep the backups until they expire" (the newest
    backup plus the longest rule of the machine's retention, read as time) or "Delete the machine
    and its backups", with the hostname typed and a recent sign-in. The machine leaves every list,
    picker, dashboard and count and its backup job; its runs, reports and audit entries stay. The
    worker deletes its restic repository (endpoints/<id>/) on every target that holds files of it:
    the primary, its copies and retired primaries. Deleting now is refused while a legal hold over
    the tenant or an unresolved suspicious restore point holds the backups, and the worker waits
    for such a hold when the backups expire. Objects the storage still locks (S3 Object Lock, a
    directory's deletion delay) are deferred until their lock runs out, recorded like a refused
    prune and left out of the lock renewal. The machines page lists the removals still pending,
    with the date, the hold or the lock. Every step is audited. Database migration 0064 adds the
    removal state to endpoints.
  • Machines: an uninstall that waits for a machine that is off now offers "Revoke now", and a
    machine without contact for longer than a configurable number of days (default 30, under Alerts
    of the machine) suggests revoking it, on its page and among what needs attention (#65). The
    machine's detail panel on Inventory shows the suggestion as a state and offers "Revoke now" and,
    once the machine is revoked, "Remove from Restow" as well.
  • Repositories: a warning when a directory repository lies on the system disk of the Restow
    server, the disk under the operating system, Docker and the database (a full system disk stops
    everything, as on 16 October 2026). The api recognises it from inside its container by device
    and block device of the path, the installation default and the mounter's shares included; it
    is shown on the Repositories page, in the "Backups land in" line of the job editors and on the
    dashboard's storage tile, where provider admins also see the free space, its trend over the last
    week and when the disk would be full. The api now also watches the system disk for low disk
    space. Nothing is blocked.
  • Microsoft 365 group mailboxes as protected objects of their own kind group (docs/MICROSOFT.md
    "Gruppenpostfächer"): the calendar and the conversations of Microsoft 365 groups and of the
    groups behind Teams. The directory sync reads groups/delta as a second delta stream next to
    the users (a full enumeration on the first and every full sync, only changes in between, its
    delta link stored with the rows), keeps only Microsoft 365 groups and orphans removed ones.
    Group mailboxes are opt-in: the protection rules get a switch "Protect all Microsoft 365
    groups" (groups: selected by default, or all), and single groups can be included in the
    list of protected objects. A mail job with scope "all" covers every protected group, like
    sites. Group mailboxes never count as protected mailboxes.
  • Group mailbox backup: the group calendar through the same calendar code as a user's (series
    masters with their exceptions), falling back to the group's calendarView and one read per
    series master when Graph refuses the event listing to the app; a calendar Graph refuses
    entirely is a warning on the run, not a failure. Every post of every conversation is stored as
    an RFC 5322 message under mail/Conversations (with its file attachments when Graph hands them
    out, otherwise their absence is recorded); only threads with new posts are read again. A group
    that no longer exists fails with the new cause graph.group_unavailable. Migration
    0065_group_mailboxes (an enum value only).
  • Group mailbox restore: the restore explorer lists groups in the "SharePoint & Teams" section
    with the areas "Group calendar" and "Conversations"; download (EML, JSON) and export (EML,
    MBOX, PST) work as for mailboxes. A restore into a user's mailbox brings back events and
    conversations; a restore into the group brings back calendar events only, because Microsoft
    Graph lets no app post into a group conversation (each post is reported as not restorable,
    with the ways that work). Restoring a group is no impersonation. The integration API reports
    lastSuccess.groups and ObjectKind includes group (integration API contract 1.6.0,
    additive; clients that handle object kinds exhaustively should accept the new value), and the
    dashboard lists group calendars and conversations among the last backups. No new Microsoft permission is needed:
    Group.Read.All and Calendars.ReadWrite were always required.
  • Start now and Stop on every row of both job lists (Servers & clients and Mail & SaaS) and in
    the row's "…" menu: one button of a fixed size that says "Start now", "Stop" while the
    job's backups run or wait, and "Stopping…" once asked. Stopping asks first and says what it
    means for the kind of job. New API routes: POST /api/v1/backup-jobs/:id/cancel (every
    queued or running backup of a mail, machine, share or copy job in one set-based request;
    audited as backup_job.run_cancelled on the job and per machine),
    POST /api/v1/pve/jobs/:id/run (a backup of every guest a Proxmox VE job covers, like its
    schedule would, without moving the schedule; pve.job.run_requested) and
    POST /api/v1/pve/jobs/:id/cancel (pve.job.cancelled). For tenant administrators and
    provider roles that may operate, closed in the public demo.
  • Detail panels on Inventory and on the job lists, like the one of VMs & containers: a click on
    a row, its name or its state opens it (?machine=<id> on Inventory, ?job=<id> on the job
    lists, so a link opens it). It lists every state, the full error and warning texts of the
    newest backup or failed run in a copyable monospace block (for a machine also the end of the
    log), what needs attention, the restore checks, the key facts, the newest runs and the
    actions.

Changed

  • Dependencies: major update of the translation libraries, i18next 26 and react-i18next
    17 (updated together). Texts, plurals and number and date formats read exactly as
    before in English and German.
  • @azure/msal-node is no longer a dependency: nothing used it. The Microsoft 365 app
    tokens, the admin consent and the IMAP OAuth2 sign-in use Restow's own token client,
    unchanged.
  • Public demo: the health checks of postgres, Dovecot and the api run every 2 to 5 seconds
    instead of every 10 to 15 (with the same grace period), and the full reset stops the old
    project with a 10 second timeout, so a reset waits less for services that are already ready
    or about to be discarded.
  • Inventory and the job lists keep their layout like VMs & containers: fixed column widths,
    one row height (loading rows included), one compact state badge per row (the most urgent of
    what applies; green only for a passed restore check), the progress of a running backup beside
    it, one-line cells without tooltips, and action buttons of one size. Columns that do not fit
    a screen give way from the right; the panel has everything.
  • "Run now" of a job is called "Start now".

Fixed

  • Public demo: reset.sh now reads RESTOW_DEMO_COMPOSE_FILES from deploy/demo/.env as the
    README always said, not only from its environment, and logs which compose files a run uses.
    A list from .env that would publish web on every interface (the own-VM override with
    80/443) is used only together with the new RESTOW_DEMO_PUBLISH_PUBLIC=true, so a co-hosted
    host whose .env carries that line keeps running as before; entries that are not compose
    files in deploy/demo/ are refused before anything is stopped.
  • Restore explorer: a mail message stored as JSON (too large for a plain message) no longer
    shows an empty <subject>.attachments folder next to it. Its attachments are restored with
    the message and were never listed; the folder row the backup records for them is now hidden
    from the listing, the folder tree and search as well.
  • The job dialog of Proxmox VE: on a phone (390 px) the three restore-point fields stack, so
    "Monatliche Sicherungsstände" no longer runs over the dialog's edge.

Security

  • The setup wizard accepts the Entra tenant for Graph mail only as a tenant id (GUID) or a
    verified domain, as Settings already did; anything else is refused (422) before it can reach
    the token URL. The URL was never open to another host (the value is URL-encoded, the login
    host is fixed), but a value such as .. changed its path.
  • An IMAP OAuth2 secret is refused unless its tenantId is a tenant id, a verified domain,
    common, organizations or consumers, and its tokenEndpoint is an https URL. Neither the
    API nor the UI creates such secrets yet; the token request will also need the address policy
    of IMAP connections before XOAUTH2 is offered.

Upgrade Notes

New images and three database migrations; no new required environment variable, and the
docker-compose.yml of 0.4.0 stays.

  • Three database migrations run at the api's start: 0063 adds three nullable columns to the
    license table, 0064 the removal state of a machine to endpoints (three nullable columns
    and a partial index over the removals that are due), 0065 the protected object kind group
    (an enum value only). None of them rewrites a table.
  • Installed licence keys keep working unchanged: every key issued before 0.4.5 is a beta
    licence and covers every 0.x and 1.x release. From now on, an image started with a key that
    does not cover it stops before the migrations and says so in the log;
    RESTOW_RUN_AS_COMMUNITY=1 starts it as Community instead (docs/LICENSING.md).
  • Group mailboxes are opt-in: after the update no group is backed up until the protection
    rules switch "Protect all Microsoft 365 groups" on or single groups are included. The first
    directory sync after the update reads the groups of every Microsoft 365 source once in full.
  • Rollback to 0.4.4 after the migrations was not tested: take a database backup before the
    update and restore it to go back.

Known Issues

  • Group calendars and conversations were tested against a simulated Graph API, never against a
    real Microsoft 365 tenant; which calendar reads Graph allows an app on a group can differ by
    tenant (the backup falls back to calendarView and reports what it could not read).
  • Machines removed from Restow cannot be restored from in the interface while their backups
    are kept until expiry.
  • IMAP sources with OAuth2 still cannot be created in the API or the interface.
  • The known issues of 0.4.4 still apply.

Verification

Before the tag, on the release branch (0.4.4 plus the 0.4.5 workstreams): lint and typecheck
of all workspaces, the unit and Postgres suites of every package on Postgres 16 (with the
Postgres guard), the web DOM tests, the v1 OpenAPI test, drizzle-kit without drift, the Go
tests of the agents, the server installer and demo reset tests and the third-party notices.
The release smoke ran on the release branch; no real Microsoft 365 tenant was used before the
tag.

Release pipeline, 2026-10-23:

Check Result Duration
1. Install: images, compose up, migrations (new install and upgrade) PASS 89s
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 19s
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 09s

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.5
ghcr.io/restow-backup/restow-web:0.4.5
ghcr.io/restow-backup/restow-community:0.4.5
ghcr.io/restow-backup/restow-web-community:0.4.5

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

restow: sha256:15e51d89e8828e007805b46244f9065e6164ddf9cfe5fd37c308b60fb5084407
restow-web: sha256:314f4e81b79123c3d85c7d2f3b13c56eb78e2edc247a2a6a3109db9093146490
restow-community: sha256:4f54044a48db51a8ffd53507a785c8ac194134f52dc381ae69fddc19c5d6b311
restow-web-community: sha256:029cdf76464d466c6d800b39b327401ede640f2dbd72bb330173cbdb14e01260

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-23T08:21:30Z

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.5 \
  --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.5 \
  --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.5 \
  --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.5 \
  --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.5 and ghcr.io/restow-backup/restow-demo-dovecot:0.4.5 (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).