Release notes / 2026.10.16

Early access release

Moorhold 2026.10.16 Replaced

Published

Release state

Replaced #

This was the Latest release until 2026.11.2 replaced it. Before it became Latest, we updated our own Moorhold server to it from 2026.10.14, 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 replaces 2026.10.15, which wasn't published. It has everything 2026.10.15 was going to bring, with five fixes made after 2026.10.15 was tested. New and Changed describe it as it now works. This release changes what you see while an update installs: once a server runs it, an update shows each step in a window that holds the portal, and keeps asking while Moorhold restarts. An admin sees a warning on the Launchpad, and a line in sudo moorhold status, when the restore drill fails or hasn't passed for more than 8 days. A web service in your Stack can declare metrics, which Superset shows as saved metrics when their mart lists readers. An agent can list and run the ones on a mart with a row-level rule. A Stack without DataHub now has an Assets page that searches its own tables and marts. On a server, the Download the sample data button on the first-run page now works. A local preview of Moorhold for the Mac is still in this release's source. It isn't public, and there's no download.

https://moorhold.dev/releases/2026.10.16

Before you update #

What changes
Once a server runs this release, an update shows its progress in a window that holds the portal while Moorhold restarts. A Stack can declare metrics, which Superset saves for a mart that lists readers and an agent's tools can run on a mart with a row-level rule. A Stack without DataHub gets an Assets page of its own. The Download the sample data button now works on a server. Moorhold for the Mac is a local preview that isn't public. It replaces 2026.10.15, which wasn't published.
Downtime
Moorhold is unavailable from when the update stops the running release until the new one has started.
Backup
Yes, on a server with backups on, which is the default: before it changes your Stack or the running release, 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 a server running 2026.10.14. If you're updating from an earlier release, read 2026.10.14's Updating first, and the Updating of any release between.
Still to be tested
Owed: a failed restore drill on the Launchpad, a metric run through an agent, the Assets page on a core server with the sample, a rollback and a restore drill on a server that holds kept copies, and the updates from releases before 2026.10.14. Also owed: the Updates page offering 2026.10.16 once it's the latest release, the update window on the next update, and the Mac preview on a Mac.

Updating #

On a server running 2026.10.14, update from the server's command line with:

sudo moorhold upgrade 2026.10.16

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. You ask for it and follow it on 2026.10.14's Updates page, which has no progress window and doesn't change by itself. Once Moorhold has restarted on 2026.10.16, a portal page you open or reload shows the window described under New until the update ends, and if it's still open then, the result. The whole update shows in the window from the update after this one.

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.16/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.

If you're updating from a release before 2026.10.14, read 2026.10.14's Updating as well, and the Updating of any release between.

What else this update changes:

  • Your web services' load files. Each web service's load pipeline in Airflow is written again once, with the same behaviour, so that it names the warehouse tables it writes and reads. See New.
  • A read-only login for metrics. The update makes a login in the warehouse that can read the marts and nothing else, with a new secret generated on the server. It's made again on every start, and it gets read access to a mart when the mart is built. See New.
  • A volume for the restore drill's record. The backup service keeps the drill's outcomes on a small volume of its own that the portal reads and can't write to. When the backup service starts after the update, it copies in the drills this server has already run. So if the last one failed, or none has passed for more than 8 days, an admin sees the warning straight away. A server with no drill on record raises none until one has run, or until 8 days have gone by. A short job runs before the backup service starts and makes sure the backup service owns the volume.
  • A server on the core profile gains a lineage service. A Stack without DataHub as its catalog now runs moorhold-lineage, a small collector that stores the lineage events Airflow sends, with its own database, two new secrets and a volume for the events. A Stack with DataHub as its catalog doesn't. No page in the portal shows what it stores. See Still known.

New #

  • An update shows its progress. When an admin has approved an update, a window holds the portal while it installs. It shows the step the server is on: checking the release, downloading it, taking the rollback point, restarting Moorhold, finishing, and checking that the backups restore. It lists those six steps on every server: see Still known for a server with backups off. While Moorhold restarts, the window says so and keeps asking. When the portal answers again, it shows the result by itself, or asks you to sign in again if your sign-in ended while Moorhold restarted. If the portal stays away for a long time, it says the restart is taking longer than usual, names the update log on the server and offers Close. The result says whether Moorhold is now on the new release, the manual steps if there are any and a link to the release notes, or why the update wasn't installed. The Updates page is where you ask for the update, as before.
  • A warning when the restore drill fails or is overdue. The restore drill backs each database up, restores it into a scratch database and compares row counts. An admin now sees "The restore drill failed" on the Launchpad, with the date, the reason and the command to try again, when the newest outcome is a failure. They see "The restore drill is overdue" when no drill has passed for more than 8 days; the drill runs every Sunday. There's no dismiss button, and a passing drill clears the warning. sudo moorhold status and sudo moorhold backup status print the same sentence after "Warning:". Members who aren't admins don't see the Launchpad warning.
  • Metrics in the Stack. A web service can declare metrics beside its marts: counts, sums, averages, minimums and maximums, ratios, comparisons with an earlier period and expressions, each over one mart, with an owner, a format and the columns it may be sliced by. A mart lists the Keycloak groups that may read it under readers, or under rowLevelAccess when it has a row-level rule. A mart with no readers is read by no one through metrics. An agent can run a metric only on a mart with a row-level rule. A metric the Stack can't accept is reported in one sentence and the web service isn't accepted until it's put right.
  • Metrics in Superset. The Stack's metrics are saved as metrics on the matching datasets in Superset, from the same definitions. A metric on a mart with no readers isn't saved, and the Sources page doesn't call that drift.
  • Metrics for agents. The portal's MCP server has two new tools, list_metrics and run_metric. list_metrics lists the metrics you may run, who owns them and the columns each can be sliced by. run_metric runs one as the signed-in person, read-only, slicing by up to four of the columns the metric declares, and returns at most 1,000 rows. The tools serve only metrics on a mart with a row-level rule, to people in a group listed under that rule's readers. A mart's own readers lets Superset save its metrics, and isn't enough for the agent tools. Someone who may run no metric gets an empty list, and a made-up name gets the same answer as a metric they may not run. The tools are offered only where the server has the read-only login described under Updating.
  • An Assets page without DataHub. On a Stack that doesn't run DataHub, which is the core and light profiles, Assets searches Moorhold's own catalog of your tables, marts, columns, sources, pipelines and checks, by name and description. Each entry has a page with its owner, description, columns and the latest outcome of the checks on a table, never the measured value. Everyone who signs in with single sign-on sees the same names and descriptions. Descriptions and owners come from your Stack. The page lists what the catalog doesn't have, such as tags and column-level lineage, and the columns of a loaded table appear after its first load. A Stack with DataHub is unchanged and keeps reading DataHub.
  • Airflow knows the warehouse tables. A web service's load pipeline now declares the tables it writes, the tables its checks read, and the tables its marts read and write, as Airflow assets. Airflow's Assets page lists them as moorhold_warehouse.<schema>.<table>, and Airflow's lineage events name those tables as inputs and outputs of each run.
  • Updates in the Mac preview. In the Mac preview, an admin sees a button in the window's title bar when an update is ready. It says "App update ready" for the app, using Sparkle, and "Moorhold <version> is ready" for the Stack, and the Stack's button goes to the Updates page. The Updates page calls the Stack "a preview build" and offers a newer release when one is known. A preview build isn't updated by itself. The app and its disk image are named for the release they are built from. There's still no download, and the app isn't part of the signed release.

Changed #

  • The installer offers the sample data and doesn't load it unasked. A fresh install now asks "Load the sample data, Moorhold sample: AI Release Radar? You can remove it later. [y/N]" and the answer is No unless you type y. --sample-data loads it, and --no-sample-data says no without asking. With no flag and no terminal, the sample isn't loaded. An update keeps what the server already has, and an admin can add the sample later from the first-run page or with sudo moorhold sample-data add. Earlier releases loaded it unless you said no.
  • How long the sample data takes. The first-run page now says loading the sample can take up to about 10 minutes in all, on a server as well as in the Mac preview, and the app's own sample messages say about 10 minutes. The installer's line for the first sample load says about 10 minutes too. On our test server a sample load took about 15 minutes, so that figure is low: see Still known. Where the page shows the command to run on the server instead of the button, it says about 10 minutes as well. Two other messages are reworded: the Assets page's line about lineage, and the message for a component that can't be chosen.
  • What the installer and rollback say while they work. The installer's server check now prints what it's looking at first, and that you can leave it running. The note about pulling images names the test its time came from and calls it an estimate, and on a smaller profile it says there are fewer images. The note about starting the containers names its test too and calls its time an estimate. sudo moorhold rollback prints "Step n of N" as each step starts, with no time.

Fixed #

  • "Download the sample data" on a server did nothing. The button was shown on a server's first-run page but was meant for the Mac preview, and pressing it did nothing. It now works. An admin presses it, and another admin approves it; on a server with one admin, that admin's own approval is enough. The other admin's page has Approve and Cancel. Adding the sample restarts Airflow's scheduler, so a pipeline that's running at that moment stops, and the page says so. It doesn't restart the portal, so nobody is signed out. It's refused if the sample is already there. Without the host's doorbell, the page shows the command to run on the server, with "Check again", as before. Controls that are meant to be hidden now stay hidden everywhere.
  • An update that stopped part-way. An update that was left at "installing" because the server stopped is settled the next time an approved update runs: it's recorded as failed, or as updated with a warning if the server already runs the release it asked for. An update that throws is recorded as failed.
  • The Updates page on a preview build. In the Mac preview, the Updates page told a preview build it was on the latest release while newer releases existed. It now says it's a preview build, and offers a newer release when one is known.
  • Adding the sample keeps people signed in. Adding the sample used to restart the portal, which could sign everyone out. It now changes only Airflow's scheduler, so nobody is signed out. If Moorhold can't renew a sign-in just then, you stay signed in and are asked to try again in a moment. A first-run page left open can still stop following the load: see Still known.
  • A rollback leaves kept copies alone. sudo moorhold rollback used to replace the copies that earlier rollbacks and restores kept, and keep each of them again under a longer name. It now leaves them as they are and says so before the plan. sudo moorhold backup restore-server skips them too. The restore drill's scratch database now has a name that fits in 63 bytes, so it no longer fails on a kept copy's long name.
  • sudo moorhold status | head -3 ends quietly. It used to end with an error trace. See Still known for commands that change the server.

Verified #

  • Unit and golden tests: pass, on the release commit's own check run.
  • Images: every image passed the licence check, and each image is the one the manifest names.
  • The signing drill: a restore drill of 2026.10.16's images passed on the release commit, on the core profile.
  • On our test server: the update from 2026.10.14 by the installer took a rollback point first and ended with every service healthy, and the restore drill passed after it. The server kept its data and settings, and its earlier backups are still listed. With two admins signed in, adding the sample from the first-run page left the portal running and kept both signed in, and removing and adding it again from the command line works. The read-only login can read a built mart and can't change it. A metric over a column its mart doesn't have is refused with one sentence, and Superset saves none of the sample's metrics. The drill volume belongs to the backup service after the update, and sudo moorhold status | head -3 ends quietly.
  • On a test machine: a core server on 2026.10.14 updated to 2026.10.16, both by sudo moorhold upgrade and by the installer, then rolled back to 2026.10.14 with "Step 1 of N" as its first line of work. Running the installer again says there's nothing to update.
  • Owed: a failed restore drill on the Launchpad, a metric run as a person through an agent, the Assets page on a core server with the sample, a rollback and a restore drill on a server that holds kept copies, and the updates from releases before 2026.10.14. Also owed: the Updates page offering 2026.10.16 once it's Latest, the update window on the next update, and the Mac preview on a Mac.

Images #

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

Still known #

  • Pages left open while the sample loads. A first-run page left open while the sample is added can stop following the load. In our test one went blank and one stopped at an early step. Nobody was signed out. Reload the page to see where the load is, and don't press Load it now on a page that hasn't moved, because it can start a second load.
  • The sample data takes longer than the page says. The first-run page and sudo moorhold sample-data add say about 10 minutes. On our test server it took about 15 minutes from approval, most of it building the dashboard's tables.
  • DataHub doesn't show what the sample load writes. DataHub shows the sample's load task, but not the tables it writes. Airflow's Assets page lists them.
  • The sample's metrics aren't saved or run. The sample data declares seven metrics, but its marts list no readers and have no row-level rule, so Superset doesn't save them and no one can run them through an agent. On a Stack of your own, Superset saves a mart's metrics once the mart lists readers, under readers or under its row-level rule. An agent can run them only on a mart with a row-level rule.
  • Piping a command that changes the server into one that stops reading. sudo moorhold status | head -3 now ends quietly. A command that changes the server, such as sudo moorhold rollback or sudo moorhold upgrade, run into head or another command that stops reading early, can still be stopped half done, because the programs it runs end when the reader goes. Don't pipe a command that changes the server.
  • The update window with backups off. On a server with backups off, the update takes no rollback point, but the window lists "Taking the rollback point" and ticks it as done once the update has passed it.
  • Metrics on the native Assets page. The page says it lists metrics, but no metric appears on it.
  • Lineage on a Stack without DataHub. On a Stack without DataHub, the Assets page shows no Lineage column or link, and says "The portal doesn't show lineage for this Stack." The Lineage item in the portal's menu is still there, and its page says no DataHub catalog is configured. The lineage service stores Airflow's events, and no page shows them.
  • Changing the catalog after install. A Stack that still declares the DataHub component can't read the native catalog, and the render says so. Changing the catalog after install isn't available in this release.
  • Two lines on the native Assets page ask you to reload. Where the catalog is still being built, or is empty, the page says to reload it to check again. It doesn't check by itself.
  • 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.
  • 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.
  • The words reconciler and reconciled. The pass summary after "Update the tools now", such as "3 resources reconciled", and its refusals, a Waiting reason that ends "on the next reconcile", an agent's reply to a new proposal, the audit log and Moorhold's own logs still use those words.
  • 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.16.tar.gz774007b8dda8c707ccefeae99ac25dc1576239f33ceeb89b131d683bf5c5ced5
manifest.yamla02739380c6db8ce76054e033acf96e156fd5d96e1aa53609da4d53b9f134db9
release.locke3f344caa3f58584ce4a93a182ba4c573910490dcd1cc8da0450766a8415c325
install.shfe17988721c7b3872a940df54f1cd17a4c837f810391cf361c13e74807c4c7f5
cloud-init-ionos.yaml65d9b38f307c59a67bb652e8f4e1347bb9bd2e8bff5503a346446211d7323b8b
cloud-init-hetzner.yaml0f05f2536412e0cc949681aa6389bc0e5f3e55b161f6aa7e901c26e6f842fcd6
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