Release notes / 2026.10.9

Early access release

Moorhold 2026.10.9 Replaced

Published

Release state

Replaced #

This was the Latest release until 2026.10.10 replaced it. Before it became Latest, we updated our own Moorhold server to it from 2026.10.8, 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 signs you out of DataHub when you sign out of any Moorhold tool, and Superset now asks you to sign in again once your Moorhold session has timed out. It fixes --check on Ubuntu, and running the installer again now keeps the server's profile. 2026.10.8's notes listed both. It doesn't yet fix the restore drill that can stop an install finishing, which is under Still known. Admins can now set a temporary password for someone on the portal's new People page, and DataHub shows the tables in Trino with their columns.

https://moorhold.dev/releases/2026.10.9

Before you update #

What changes
Signing out of any Moorhold tool now signs you out of DataHub too, and Superset asks you to sign in again once your Moorhold session has timed out. Admins can set a temporary password for someone in the portal, and DataHub now shows Trino's tables with their columns.
Downtime
Moorhold is unavailable from when the update stops the running release until the new one has started. That was measured on this release's updates from 2026.10.7 and from 2026.10.8, by the installer and by sudo moorhold upgrade.
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.
Still to be tested
Superset's session timeout and the cases that sign people in through an organisation's own sign-in are still to be tested, as is removing a lake restore's folders (no lake-profile server has run this release yet) and the Updates page offering 2026.10.9 once LATEST moves.

Updating #

On a server running 2026.10.7 or 2026.10.8, update from the server's command line with:

sudo moorhold upgrade 2026.10.9

It checks the release and the server before it changes anything, and takes the same rollback point as the installer. Once this release is the latest one, an admin can also press "Check for updates" on the Updates page in the portal and ask for the update there.

On a server running 2026.10.7 or 2026.10.8, you can instead 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.9/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.

New #

  • "Forgot your password?" on the sign-in page. The sign-in page now has a "Forgot your password?" line. It opens in place and says to ask another admin to reset your password. If you're the only admin, it gives the command to run on the server, sudo moorhold users reset-password <username>. It doesn't show on a Moorhold that signs people in through your organisation's own sign-in.
  • Temporary passwords in the portal. Admins have a new People page in the portal, which lists everyone who signs in to this Moorhold. If people sign in through your organisation's own sign-in, the page says so, and passwords are reset there. For someone who's forgotten their password, an admin can set a temporary password there. The portal makes it up and shows it once. The person signs in with it once and then chooses their own, and their authenticator app still works. If you signed in a while ago, the portal asks you to sign in again before it sets one. You can't set one for yourself, and the local admin account doesn't see the page.
  • A lost authenticator app. sudo moorhold users reset-password <username> --reset-sign-in also removes the person's authenticator app with its recovery codes. It ends their sessions too. They set up a new authenticator app at their next sign-in. Anything else they still had to do at sign-in stays. If the command can't finish, it says so, and running it again finishes it.
  • Trino's tables in DataHub. DataHub now reads each catalog Moorhold sets up in Trino, so your tables and views show in DataHub with their columns. Before, DataHub knew only the tables a pipeline's lineage named, without their columns. It reads them again on a schedule. A table you drop from Trino leaves DataHub's search after the next read that succeeds, and keeps its documentation and lineage. A read that would remove more than three quarters of a catalog removes nothing. Trino's own system tables are left out. To turn it off, set trinoIngestion: false in the DataHub component's overrides in your Stack. The tables DataHub already shows stay.
  • Apply your own edits to the Stack. After you edit /opt/moorhold/stack/stack.yaml, sudo moorhold apply puts your edit in force. It starts the stack again with the edit, applies it and prints what changed. It uses the profile the server runs unless you give --profile. Before, moorhold apply on a server stored the Stack in a file that nothing reads, and said it had worked.
  • Remove what a lake restore kept. A lake restore keeps the data it replaced in a folder on the server, as big as the lake was. sudo moorhold backup drop-kept now lists those folders with their sizes beside the kept databases, and removes them once you say yes. It leaves alone a folder from a restore that stopped halfway, since that may hold live data. sudo moorhold status lists the folders, and a lake restore's last line now gives the command that removes them.

Fixed #

  • Signing out of DataHub. This is a security fix. Signing out of any Moorhold tool now signs you out of DataHub too. Before, signing out of Superset or Airflow left DataHub signed in until its own session ran out. The next page you open in DataHub asks you to sign in, and signing in brings you back to it. The signed-out page no longer says that tools in other tabs may keep you signed in. A DataHub session that started before the update still lasts until it runs out. 2026.10.8's notes listed this as still known.
  • Superset after your session times out. This is a security fix. Superset now asks you to sign in again once your Moorhold session has timed out. Before, it kept you signed in until you closed the browser. While your Moorhold session is still going, Superset signs you in again by itself and comes back to the same page, but that reloads it, so anything you hadn't saved in a chart or a dashboard you were editing is lost.
  • Checking a server with --check on Ubuntu. On Ubuntu, sudo bash install.sh --check stopped with "Permission denied" after its downloads. It now runs its checks there. It still installs nothing, and it unpacks what the check needs into a folder under /var/lib that it removes when it ends. 2026.10.8's notes listed this as still known.
  • The installer keeps the server's profile. Running the installer again on a server that runs Moorhold, for example to move it to another hostname, now keeps the profile the server runs unless you give --profile. Before, it asked for the profile again on a terminal, and without a terminal it assumed the full profile, so on a 16 GB server it stopped at the memory check. 2026.10.8's notes listed this as still known.

Verified #

  • Unit and golden tests: pass.
  • Images: every image passed the licence check.
  • On the test servers: the update from 2026.10.8 and from 2026.10.7, by the installer and by sudo moorhold upgrade, each ends on 2026.10.9, takes its rollback point, keeps the server's settings and the data marker, and passes the restore drill afterwards. sudo moorhold rollback put a test server back on 2026.10.7 with the rollback point's data. The updates stop the running release until the new one has started, as Updating says.
  • On a fresh install: core, on stock Ubuntu 24.04, and install.sh --check on stock Ubuntu: the checks run and pass, and the check installs nothing and leaves nothing behind. The installer run again for a new hostname, on a terminal and without one with --change-hostname, keeps the core profile and asks no profile question. The signing drill passed.
  • In the portal: the People page's temporary password, --reset-sign-in with a pending Verify Email, the sign-in page's password help, signing out of DataHub, and sudo moorhold apply.
  • Owed: Superset's session timeout; the cases with an organisation's own sign-in; removing a lake restore's folders (no lake-profile server has run this release); and the Updates page offering 2026.10.9 once LATEST moves. Trino's tables in DataHub don't work; see Still known.

Images #

Every one of Moorhold's own images is rebuilt from this release's source. No tool changes version, and the upstream images keep the digests they had in 2026.10.8.

Still known #

  • A restore drill that never finishes. Rarely, a restore drill and a data load, such as the sample data's, wait on each other for ever. That happens when the load starts to replace a table the drill is reading. If it's the drill at the end of an install or update, that install or update never finishes. Neither finishes by itself, so from a second terminal on the server, stop the load's waiting step:
    sudo docker compose -f /opt/moorhold/project/compose.yaml exec -T postgres psql -X -U postgres -d moorhold_warehouse -c "SELECT pg_cancel_backend(pid) FROM pg_stat_activity WHERE usename = 'moorhold_loader' AND wait_event_type = 'Lock'"

    The drill then finishes, and so does the install or update. The load stops with an error and keeps the data it had. It runs again at its next scheduled time, and you can start it sooner in Airflow. 2026.10.8's notes said this release would fix it. It doesn't yet, and we're working on a fix.

  • Running the installer again on this release. Running this release's installer without --hostname on a server that already runs it prints the installer's usage. There's nothing to update.
  • 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.
  • Working only in Airflow or Superset. Time spent in Airflow or Superset alone doesn't keep your Moorhold session going, so if you use only one of them until the session times out, you see the sign-in page.
  • API tokens made in Airflow. They keep working after you sign out, until they expire or are deleted in Airflow.
  • System tables for agents. Agents that search through DataHub's own MCP server still see the system tables, because DataHub applies its default view only on its own pages.
  • Docker's lines during an update. An update still shows Docker's own output while it pulls the new images.
  • A reboot after a rollback. 2026.10.7 and earlier releases can't stop Moorhold at shutdown. So after a rollback to one of them, a reboot shows services failing and restarting until Moorhold has started, as before. They recover by themselves.
  • 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.
  • Trino's tables in DataHub. The new ingestion that brings your Trino tables into DataHub doesn't work yet: each catalog's read stops with a certificate error, because DataHub doesn't trust Trino's own certificate, so no tables show. To stop the reads that fail, set trinoIngestion: false in the DataHub component's overrides in your Stack. We're working on a fix.

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.9.tar.gzebb2532387ae99d6ebb25306a5ed9356870e59cc63c1fa2c16c603ce66c69351
manifest.yaml6a03b2098479378121eed7cbec245d66d77cb686ff43819d021bb642bdd59556
release.lockc81f95e15132368dfa82b0ec76ecf1ecc337ff707c70a6918721fa493b2d716d
install.sh5b90be8c3c08c5e320c3fb8a654c3f4f92b36f56b6712f1326f1d3751196d250
cloud-init-ionos.yaml73f9c83c8320d8a30ad6091a7604233a1b4df0a927dd91524a5394bfe689a09f
cloud-init-hetzner.yamle0ecabe1f6eda25130b959bed449b183f52c26f97ffc513bc3f33f63befff058
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