Release notes / 2026.10.11

Early access release

Moorhold 2026.10.11 Skipped

Published

Release state

Skipped #

We won't make this release Latest. 2026.10.12 reached Latest first and has everything in this one. 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.

This release fixes the restore drill that could wait for ever on a data load, which the last three releases' notes listed as still known. After an update, the sign-in page keeps Moorhold's design, and the launchpad's health lines for Superset, DataHub and your account read right. The first sign-in after an install now leads to your first dashboard, with a guided first pipeline you can take if you want to. An admin can set the server's own mail settings in the portal, and you can have DataHub and Superset sleep while nobody's using them, so the server has more memory for everything else.

https://moorhold.dev/releases/2026.10.11

Before you update #

What changes
A restore drill can no longer hang on a data load, and Moorhold's sign-in page keeps its design after an update. The first sign-in now leads to your first dashboard, with an optional guided first pipeline, an admin can set the server's own mail settings, and DataHub and Superset can sleep while nobody's using them.
Downtime
Moorhold is unavailable from when the update stops the running release until the new one has started. It hasn't been measured for this release.
Backup
Yes, on a server with backups on, which is the default: 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. If you've turned backups off, the update takes no rollback point.
Manual steps
None for most servers. If you added a data source in the portal or with `moorhold apply -f`, run sudo moorhold apply once after the update, and if you changed the sample data's source file, see Updating.
Still to be tested
This release is still to go through its test servers: the updates from 2026.10.10 and 2026.10.9, a rollback after the update, a fresh install with the sample data, and everything listed under New and Fixed are still to be tested, as is the Updates page offering 2026.10.11 once LATEST moves.

Updating #

On a server running 2026.10.10 or 2026.10.9, update from the server's command line with:

sudo moorhold upgrade 2026.10.11

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.10 or 2026.10.9, 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.11/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. On a server that already runs this release, it says there's nothing to update and changes nothing.

The update recreates Keycloak, the service behind sign-in, one time, so that it picks up Moorhold's sign-in design again (see Fixed).

If your server has the sample data, the update changes it to this release's sample, which no longer includes figures from GitHub. Before it starts the new release, it writes the sample's source file again, keeping the old one beside it. Once the new release is up, it drops the sample's three GitHub tables (gh_repo, gh_release_month and tool_release_trend) from the warehouse, removes them from DataHub, and says which it dropped. Superset drops the "Releases per month" chart. It keeps the tables if the sample's source file has been changed since Moorhold wrote it, if it still declares them, or if another source loads the same schema, and says why. If you've changed the source file, the update leaves it as it is and says so. If your file still asks for the GitHub tables, the sample's next load fails, because this release's sample no longer serves them. To use this release's sample source, run the command the update gives you, which replaces your changes:

sudo moorhold sample-data add

If you roll back to the release you updated from, sudo moorhold rollback puts the old sample source back, and the three tables come back with the restored warehouse or with the old sample's next load.

If you added a data source in the portal, or with moorhold apply -f, run this once the update has finished:

sudo moorhold apply

The update itself gives secrets only to the sources in your Stack file on the server. It reads the portal's sources with the release that's running, and 2026.10.10 and earlier can't list them, so it says "Couldn't read the store's sources, so only the Stack directory's are rendered." From this release on, an update and sudo moorhold apply include the portal's sources too.

New #

  • Your first dashboard. The first time you sign in after installing, the portal now takes you to "Get to your first dashboard", with three choices: explore the sample data in its ready-made dashboard in Apache Superset, build your first pipeline, or connect your own data. While the sample's still loading, the page says how far it's got and only offers the dashboard once Superset has it. Setup is shorter too, at three steps.
  • A guided first pipeline. "Build your first pipeline" is an optional lesson in four short steps, using the sample data. You bring the data in with Apache Airflow, look at it in Superset's SQL Lab, find it and its lineage in DataHub, and see it in the sample dashboard. Moorhold keeps your place, so you can leave and pick it up again from the portal's home page. It's offered only on a server with the sample, Airflow and Superset.
  • What each tool does, and the projects behind them. Each tool on the launchpad now says in a line what it does here, and "How your data flows" shows the path from bringing data in to seeing it, naming the tool for each step. The Stack page links to "What's in your stack", which lists every open-source project your server runs, with its version, licence and website, and the sample data's sources and their terms.
  • The server's own mail settings. An admin can now set the mail server this server sends email through, on the new Mail page under Platform in the portal. The page's test email button doesn't work in this release: see Still known. An admin who has signed in through the server's own sign-in can now set them. Moorhold gives the settings to Keycloak. You set the mail server's password on the server with sudo moorhold mail password, which asks for it twice without showing it and restarts the portal for a few seconds. The Mail page holds only a reference to the password and never shows it. Members can read the page but not change it. Saving or removing the settings asks you to sign in again if you last signed in more than five minutes ago, and keeps what you typed. Moorhold doesn't send password resets by email. The update gives the account Moorhold uses in Keycloak the role it needs to write the settings, as a fresh install has. The Secret copies page lists two new copies of the mail password and, if DataHub may sleep, two for the service that wakes it.
  • Tools that sleep while idle. You can have DataHub and Superset stop while nobody's using them, which frees their memory for the rest of the server. It's off unless you turn it on: under spec.public in /opt/moorhold/stack/stack.yaml add:
    sleepWhenIdle:
      components: [datahub, superset]
      idleMinutes: 30

    components names the tools, and only DataHub and Superset can sleep. idleMinutes is how many minutes without use they wait, from 5 to 1440, and 30 if you leave it out. Then run sudo moorhold power setup and sudo moorhold apply. Opening a sleeping tool shows a page that says it's starting, and opens the tool when it's ready. If you've set up DataHub's MCP server for agents, an agent's call to it wakes DataHub too, and gets an answer asking it to try again shortly. While DataHub sleeps, the portal's search says so rather than showing an error, and Moorhold waits for it to wake before it catches up. A tool has to be published to sleep.

  • The sample data no longer includes GitHub figures. The update removes the three tables built from them and the "Releases per month" chart, unless you'd changed the sample's source.
  • Which account the sign-in page is for. The sign-in page now says it's for your account on this server, separate from your Moorhold account at account.moorhold.dev, with a hint under the email field. It no longer says that the next step asks for a code from an authenticator app. A wrong email or password now says "That email and password don't match. Try again."

Fixed #

  • A restore drill that never finished. A restore drill and a data load, such as the sample data's, could wait on each other for ever, so an install or update that ended with a drill never finished. Now, if the drill waits more than a minute for a table, it lets the load go on, waits, and tries once more. If it's held up again, the drill fails and says to run sudo moorhold backup drill once the other job has finished, instead of hanging. The install or update itself still stands. The last three releases' notes listed the hang as still known, with a command to clear it, which you no longer need.
  • The sign-in page after an update. Each time Moorhold wrote its project, which an update and sudo moorhold apply do, a running Keycloak lost Moorhold's sign-in design and showed its own. Moorhold now writes the design in place, so Keycloak keeps it, and the update recreates Keycloak once to put the design back. If you ran the command the 2026.10.10 notes gave for this, you don't need to again.
  • The launchpad's health lines. Superset's and DataHub's tiles no longer show Unknown, "No answer within 2 s", while both tools are working, and your account's tile now shows the health of sign-in instead of saying Moorhold has no health check for it. 2026.10.10's notes said each tool was checked for its own health. These tiles weren't.
  • Signing back in to DataHub. After you sign out of DataHub, the signed-out page now offers "Sign in to DataHub again", which signs you in and takes you to DataHub. Before, signing in again ended on the portal. You land on DataHub's home page rather than the page you left: see Still known. 2026.10.10's notes said you'd land on the page you left. The sign-in ended on the portal instead.
  • A new source in its own schema. A data source that loads into a schema that isn't in the warehouse no longer fails each time with "permission denied for database moorhold_warehouse" on a server installed before Moorhold granted that. Moorhold now grants it each time the stack starts.
  • A source added in the portal. A data source added in the portal, or with moorhold apply -f, now gets its secret on the next sudo moorhold apply, and on every update after this one, so its load can read it. Before, only the sources in your Stack file on the server got theirs, and a load from any other failed because its secret file wasn't there.
  • A restore drill that could pass wrongly. The drill now locks every table before it counts rows, so a data load that has just emptied a table can't make it pass on a backup with that table empty.
  • The installer's words about which systems it accepts. When it refuses a system, the installer now says it accepts Ubuntu 24.04, Ubuntu 26.04 or Debian 12. Before, it read as if only Debian 12 were.

Verified #

  • Owed: Nothing in this release has been through its test servers. When it has, this section lists what was tested.

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.10.

Still known #

  • Sending a test email from the Mail page. "Send a test email" opens a "We can't find that page" page and sends nothing. Saving and removing the mail settings work, and Keycloak uses the saved settings.
  • Saving after leaving a page open. If you leave a portal page open for more than a few minutes and then save a change, you can see "Not a portal session: token expired." and nothing is saved. Reload the page, sign in again and save.
  • Signing back in to DataHub returns to its home page. After you sign out of DataHub and sign in again from the signed-out page, you land on DataHub's home page, not the page you left.
  • Signing back in after Superset's sign-out. After you sign out of Superset and sign in again from the signed-out page, you land on the portal's Proposals page. Open Superset again from the launchpad.
  • An update while a tool sleeps. The checks an update runs first count a sleeping tool's stopped services as failed, so the update refuses to start. Open each sleeping tool in your browser just before you update, and start the update straight away. An update approved for the maintenance window keeps refusing while a tool sleeps, so if you use sleeping, run your updates by hand.
  • More memory for a sleeping DataHub. If a request for more memory for DataHub's services comes due while DataHub sleeps, the resize can fail and put the old size back. If it does, open DataHub to wake it and ask again.
  • The launchpad and a sleeping tool. The launchpad can't tell that a tool is asleep, so a sleeping tool's tile can show it as not answering. Opening it wakes it.
  • 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.
  • An agent working alone. An agent's calls to DataHub's MCP server don't count as use, so DataHub can go to sleep while an agent is working with it. The agent's next call wakes it.
  • 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.
  • 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.

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.11.tar.gz8f4aca7566afab5fde68a5153afdc83e9bf60362b8b90a7371c7b3044d88da0d
manifest.yaml253c17a0a7ce8968f32d6a1b5551bc241d6e6021d6fe19f2c5c669058898a2be
release.lock8c64cbed138f9cff38a01cca54615b6a227de9d58ba607ae8b86cdd986b2a45a
install.sh1fe5ba54b3baa6cc4252ef9c60c105936d253f9e960a768d543379058b659f6f
cloud-init-ionos.yaml9f76b9207f4aa51b8537483befde6831d6dc89b7a95eca62905b62a334e230e9
cloud-init-hetzner.yamlf66c2a96901673c34d56e9cbbce57274a346b75ec1ee9f260cc9de7de9870934
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