Release notes / 2026.10.7

Early access release

Moorhold 2026.10.7 Replaced

Published

Release state

Replaced #

This was the Latest release until 2026.10.8 replaced it. Before it became Latest, we updated our own Moorhold server to it from 2026.10.6, and it passed a restore drill there. Its files stay on get.moorhold.dev and still work. We haven't tested an update from this release to 2026.11.4. If your server runs it, email hello@moorhold.dev and we'll help you move it.

We wrote this release's notes, including their Still to be tested line, before we ran it on our own server.

This release finishes signing out across Moorhold and makes sure an updated server starts again after a reboot. Signing out of any tool now signs you out of the Moorhold portal too. Admins can reset a portal password from the server's command line, and can choose to be told when a new release is ready.

https://moorhold.dev/releases/2026.10.7

Before you update #

What changes
Signing out of any tool now signs you out of the Moorhold portal too, and every update makes sure Moorhold starts again after a reboot. Admins can reset a portal password from the server and choose to hear about new releases.
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 for the update. A server updated to 2026.10.6 that restarts before it has this release needs sudo moorhold start --profile <profile> after the reboot.
Still to be tested
No test server has run this release yet. The update from 2026.10.6 and rolling it back are still to be tested, as are a fresh install and a reboot after the update. Signing out across the tools is owed too.

Before you reboot a server on 2026.10.6 #

A server updated to 2026.10.6 from an earlier release may not start Moorhold again by itself after a reboot. If it restarts before you've updated it to this release, run this once it's back up:

sudo moorhold start --profile <profile>

Use the profile the server runs, such as full. Updating to this release fixes it for good.

Updating #

To update a server running 2026.10.6, 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.7/install.sh
sudo bash install.sh

The installer sees the release that's running and updates it in place, with the same checks and the same rollback point as 2026.10.6's update. Every update now also makes sure the server starts Moorhold at boot, and says so.

New #

  • Signing out of a tool signs you out of the portal. Signing out of any tool now signs you out of the Moorhold portal too. The next page you open there asks you to sign in.
  • Reset a portal password from the server. sudo moorhold users reset-password <username> sets a new password for a portal user, and --temporary makes them choose their own at their next sign-in. sudo moorhold users list lists the portal's users. The new password is asked for twice and never shown, and each reset is recorded in the audit log.
  • Hear about new releases. Admins can turn on a daily check for new releases on the portal's Updates page, under Platform. It's off until an admin turns it on, and an admin can still check by hand while it's off. A new release shows on the launchpad, with what changes and its downtime. A release that fixes a security problem says so. The check fetches only Moorhold's signed release files. It sends no data, but our site sees your server's address.
  • An update an admin approves. On the Updates page, one admin asks for an update and a different admin approves it. With only one admin, they type the version to confirm. The server then runs the same update as the installer, with the same checks and rollback point.
  • Memory for DataHub on larger servers. A new install on a server with 28 GiB of memory or more gives DataHub and its search service twice the memory they had. A server you update keeps what it has.
  • sudo moorhold start-at-boot. Sets the server up to start Moorhold at boot, on its own. sudo moorhold status now says when that isn't set up.

Fixed #

  • Moorhold starts again after a reboot on an updated server. A server first installed before 2026.10.6 and then updated had nothing to start Moorhold at boot, so its services couldn't start after a restart. Every update now sets that up.
  • Signing out of Superset or Airflow. It now ends on Moorhold's signed-out page, which offers to sign in again, where before it showed the tool's own bare sign-in page.
  • Airflow after you sign out elsewhere. Airflow now ends your session when you sign out of another tool. Before, it went on showing you signed in.
  • The sign-out confirmation page. When Keycloak asks you to confirm signing out, its page now uses Moorhold's words and style, with a Sign out button.
  • The sign-in pages after an update. An update that changes the sign-in pages now shows the new ones straight away. Before, Keycloak kept showing the old ones until it restarted.
  • The Trino tile opens a query editor. It opens SQL Lab with an editor ready to type in, where before you had to add a tab first.
  • Rolling back with a slow Superset. A rollback no longer stops when Superset is slow to stop. Superset now stops when it's asked to.
  • The disk check before an update. It now reads the size of every database, where before it printed a Postgres error and said the size couldn't be read.
  • Client addresses in the tools' logs. The tools behind the public front now see only the shortened client address it keeps, never the full one.
  • The sample data's memory. The sample supplier now runs with a memory limit.

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.6 and rolling it back are still to be tested, as are a fresh install and a reboot after the update. Signing out across the tools is owed too.

Images #

Every one of Moorhold's own images is rebuilt from this release's source. Superset's image now hands over to its web server, so it stops when asked. The upstream SeaweedFS and Polaris images keep the digests they had in 2026.10.6.

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 until its own session runs out. 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, until its session runs out, 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, and Moorhold's own health check ignores it.
  • x86_64 (amd64) servers only.

Upgrading #

On a server running 2026.10.7 or later, update from the server's command line with sudo moorhold upgrade <version>, giving the release you're moving to. On a server running 2026.10.6 or later, you can instead download the new release's installer and run it on the server as you did to install, but without --hostname.

This release's notes give its steps under Updating, and say which releases it updates from. If they don't cover the release your server runs, email hello@moorhold.dev and we'll help. 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.7.tar.gz8de3a519b47c07b01f209a46dc54cc5bdba4f3cc89f78b7051ee3f3b5fbf3d45
manifest.yamle3e34bc6f9e810b804a8735f30b865c1dfaff5a9fe5e295015cf7821094ddf5d
release.locka4e64631b9a93e152428659f428f5da38617b211c90a8feeecb81ee92792822d
install.sh066e57c702c11e213070b536825dd5ff1f9379ba77529832761e50db349f24a9
cloud-init-ionos.yaml28cf447270d1b1f672111e309236f697b1d4fd7eb6c58371b6278448719be46a
cloud-init-hetzner.yaml2fa01b0982500f6fb57aa99f776949ee56c7d6670f6a786cc000578e12e41220
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