Release notes / 2026.10.6

Early access release

Moorhold 2026.10.6 Skipped

Published

Release state

Skipped #

We won't make this release Latest. A server updated to it may not start Moorhold again by itself after a reboot. 2026.10.7 fixes that. Its files stay on get.moorhold.dev and still work. If your server runs it, update to 2026.11.4. The update we ran on our own server started from 2026.11.3.

If your server runs 2026.10.4 or 2026.10.5, don't use the update steps below. Email hello@moorhold.dev and we'll help you move to 2026.11.4.

This release lets a server update in place. A server running 2026.10.4 or 2026.10.5 moves to this release with this release's installer, and keeps its data and settings. New installs take backups on this server by default, and every update takes a rollback point first. Signing out of one tool now signs you out of the others.

https://moorhold.dev/releases/2026.10.6

Before you update #

What changes
Servers running 2026.10.4 or 2026.10.5 can now update in place, with backups on by default and a rollback point taken before the update. Signing out of one tool now signs you out of the others.
Downtime
Moorhold is unavailable from when the update stops the running release until the new one has started. That hasn't been measured on this release yet.
Backup
Yes: before it changes anything, the update takes a rollback point, a backup of every database on this server. If the new release doesn't start, it goes back to that point by itself.
Manual steps
None.
Still to be tested
No test server has run this release yet. The update from 2026.10.4 and 2026.10.5 and a fresh install are still to be tested, with rolling back and signing out across the tools.

Updating #

To update a server running 2026.10.4 or 2026.10.5, download this release's installer and run it on the server as you did to install, but without --hostname:

curl -fsSLo install.sh https://get.moorhold.dev/2026.10.6/install.sh
sudo bash install.sh

The installer sees the release that's running and updates it in place. It checks the release's signature and the server first, and stops with nothing changed if a check fails. It asks for your access key once if the server doesn't keep one, and then keeps it. An update keeps the server's settings, so the installer refuses the flags that would change them, such as --acme.

The running release stays in place until the new one has started. If the new one doesn't start, the update restores the rollback point and starts the earlier release again.

The update also sets up signing out across the tools, so that signing out of one tool signs you out of the others on an updated server too.

New #

  • Update in place. A server running 2026.10.4 or 2026.10.5 updates to this release with this release's installer, as above. The update checks the release's signature and the server before it changes anything, takes a rollback point, edits the server's Stack in place so your own edits and comments stay, and keeps the previous Stack beside it. Later releases update in place from the server's command line, with the same checks.
  • Backups on by default. A new install takes a backup on this server every day. The install takes the first backup and a restore drill of every database, and shows the backup repository's key once. A server you update gets the same backups, unless you'd taken them out of its Stack. sudo moorhold backup status shows the last backup and the last drill, and sudo moorhold backup key shows the key again.
  • A restore drill every week. After Sunday's backup, and after every update, each database is restored into a scratch database and checked against the backup.
  • Roll back an update. sudo moorhold rollback takes the server back to the release it ran before the last update, with every database as it was at the rollback point. It shows what it will replace and asks first, and keeps the databases it replaces under dated names. --database restores one database only, and --dry-run shows the plan and changes nothing.
  • The server keeps its access key. Once the registry has accepted your access key, the server keeps its own copy, readable only by root, and deletes the file you gave it as before. Running the install again after a failure uses the kept key. sudo moorhold access-key set replaces it, and only once the registry accepts the new one. sudo moorhold access-key forget deletes it.
  • sudo moorhold status. Shows the release, the hostname, whether the server keeps an access key, the last backup and the last update, and each service's health.

Fixed #

  • Signing out. Signing out of Superset or Airflow now ends your Moorhold session, so the other tools ask you to sign in again. The launchpad's Sign out does the same, and so does an admin ending your session in Keycloak. Each tool's sign-out goes straight back to its sign-in page, without a Keycloak page asking you to confirm.
  • DataHub's Sign out. It now ends your Moorhold session and takes you to the launchpad, where before it showed an error page and left you signed in.
  • Moorhold starts again after a reboot. The server starts Moorhold at boot, so backups keep running after a restart.
  • The restore drill on a busy database. The drill no longer fails on a database that's being written to while it runs, such as Airflow's.
  • Straight apostrophes on the sign-in pages. The last messages on the sign-in pages that had curly apostrophes now use straight ones.

Verified #

  • Unit and golden tests: pass.
  • Images: every image passed the licence check.
  • Owed: no test server has run this release yet. The update from 2026.10.4 and 2026.10.5 and a fresh install are still to be tested, with rolling back and signing out across the tools.

Images #

Moorhold's own images are rebuilt from this release's source, apart from the Trino and DataHub Actions images. Their source hasn't changed since 2026.10.5, so they keep the build from that release. The upstream SeaweedFS and Polaris images keep the digests they had in 2026.10.5.

Still known #

  • DataHub after signing out elsewhere. DataHub can't be told when your Moorhold session ends. If you sign out of Superset or Airflow, DataHub stays signed in for up to an hour. Signing out from the launchpad or from DataHub itself signs you out of DataHub too.
  • DataHub on a shared computer. If the last person to use the browser didn't sign out, DataHub can still open as them, with their access, for up to an hour, even after you sign in to Moorhold as yourself. Sign out before someone else uses the browser.
  • Users and Groups in DataHub. If your role can't manage users, DataHub's Users and Groups page shows "Failed to load users!". That's DataHub's message when your role isn't allowed to see the list of users.
  • Airflow's Triggerer. Airflow shows its Triggerer as unhealthy because Moorhold doesn't run one. Nothing in Moorhold uses deferrable tasks.
  • x86_64 (amd64) servers only.

Upgrading #

Don't update a server to this release. Release state, above, says what to do instead. For help with any move, email hello@moorhold.dev. More about upgrading

Recovery steps #

There's no automatic rollback yet, so there are no recovery steps to follow on your own. If something has gone wrong with your Moorhold, email hello@moorhold.dev with the version you're on and what you saw, and we'll help. Please don't send passwords or keys.

Download and verify #

The signed release is on get.moorhold.dev. Check the signature on release.lock first, then each file's SHA-256.

FileSHA-256
moorhold-2026.10.6.tar.gzb10b0ee13dc909e8cbf00b30be5fd5b93a3d900a0d44cb0ad065a903291ff689
release.lock38750d4ed2b9b1c76e3e44965686856b16076e585995924bf289e07f514048b9
install.sh518c091b819fbb98769ddb0e237ec9a1f41aefa03fd3d66d14afc594c7e4eac7
cloud-init-ionos.yaml26e0471d0397a477e6b9ab7f1f5c479a71f9f73b3888ed691fef964a39328250
cloud-init-hetzner.yamledebe7826b28681fdcc9bed63125b875c086232d48b8430f9b9dd80ffb63901c
release.lock.minisigSignature, key 7F6D12F3F6217F9C
SHA256SUMSThe checksums above
minisign -Vm release.lock -p moorhold-release.pub
sha256sum -c SHA256SUMS

Public key: get.moorhold.dev/moorhold-release.pub