Release state
Latest #
This is the Latest release, the one we recommend. Before we marked it Latest, we updated our own Moorhold server, which runs the full profile, from 2026.11.3 to this release. It then passed a restore drill there. Get started installs it, and Moorhold's update check offers it on servers where an admin has turned the check on.
We wrote this release's notes, including their Still to be tested line, before we ran it on our own server.
This release mainly fixes starting and updating. If Moorhold fails to start when the server boots, it now waits 15 seconds and tries once more, and every start keeps a record that moorhold status and the Launchpad show. An update interrupted by a restart is settled once Moorhold is running again, and an approved update is installed once the update that was running has finished. robots.txt on the portal and published tools is now two lines, so crawlers can read its rule. Updates also get simpler: one admin is enough, an admin can approve their own proposal, and automatic updates and off-site backups are free on every server. Commands that change your server now run one at a time and say which step they're on. On a Mac, the Moorhold app shows the terms before it sets anything up, asks about the sample dashboard, checks for the network before first setup, and can update Moorhold itself.
Before you update #
- What changes
- If Moorhold fails to start at boot it tries once more and keeps a record, and an update that was interrupted by a restart is settled once Moorhold is running again. An approved update is installed once the update that was running has finished, and robots.txt on the portal and published tools is served as two lines. One admin is enough for an update, an admin can approve their own proposal, and automatic updates and off-site backups are free on every server. Commands that change your server run one at a time and say which step they're on. The Moorhold app for Mac shows the terms before it sets anything up, asks whether to load the sample dashboard, checks for the network first, and can update Moorhold itself.
- 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 apart from the copies an earlier rollback kept. 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.11.3. If you're updating from an earlier release, read 2026.11.3's Updating first, and the Updating of any release between.
- Still to be tested
- Owed: the first update installed by moorhold-requests.service, an update from 2026.11.3 to this release approved in the portal; a server that still fails to start after its second try at boot; a server restarted during an update install, settled afterwards; an admin approving an update while sudo moorhold upgrade is running; one admin asking for an update and approving it on a server with two admins; a tool dropped from a source on a server, with its catalog removed; how a server records an automatic update refused after 30 minutes, and automatic updates staying on after it; an update from the Moorhold app on a Mac that fails part way, and what the Updates page and the audit log say after an update from the app; the first setup of the Moorhold app for Mac with its terms, its sample box and its network check; the first start of the Linux system on a Mac without the two-minute wait; and the Mac app's setup log, on a Mac. Also still owed from 2026.11.3: automatic updates on a server, and a moorhold-update.timer masked before the update; an install of this release on a 12 GB server with the full profile or a 6 GB one with core, and the light profile in 4 GB; adding the lake to an installed server; the wait for a busy download server, on a server and in the Moorhold app for Mac; the Lineage menu on a Stack without DataHub; and the sample dashboard's Month column in the Moorhold app for Mac. And from 2026.11.2: the Updates page offering a release once it's the latest, the update window on a whole update, the message behind a proxy that refuses get.moorhold.dev, the updates from releases before 2026.10.16, a fresh install with the sample data, a daily backup on a server that holds kept copies, and a restore drill with a kept copy of a long name.
Updating #
On a server running 2026.11.3 with the full profile, update from the server's command line with:
sudo moorhold upgrade 2026.11.4
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.11.3, that update is installed by 2026.11.3's moorhold-requests.service, and a server with two or more admins still needs a second admin to approve it, as 2026.11.3 says. From this release on, one admin is enough (see New).
On a server running 2026.11.3 with the core or light profile, use the installer below, not sudo moorhold upgrade or the Updates page. Both run 2026.11.3's disk check, which counts every image in the new release, including the ones for tools your profile leaves out, and can refuse an update on a server that has room (see Fixed). The installer runs this release's own check, which counts the images your server runs and the images of any tool the update adds, and falls back to every image if it can't work that out.
On a Mac, open the Moorhold app once it carries this release. When the release it carries is newer than the one running, the button in the title bar says it's ready, and Update now starts it (see New). A Mac runs the light profile, so on a Mac running 2026.11.3 use that button, not the Updates page.
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.11.4/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.11.3, read 2026.11.3's Updating as well, and the Updating of any release between.
New #
- An admin can now approve a proposal they made, or one their own AI agent made, on the Proposals page. Whoever edited a waiting proposal's change can approve it too. A person still approves every proposal from an AI agent or an MCP client, in the portal, and no agent can approve anything. A scheduled analytics task about individual people is no longer held back because the person who proposed it also approved it. An upgrade of a tool is still approved by typing the tool's name.
- While Moorhold starts, it now says how many of its services are ready, and an upgrade numbers its steps. Backups, restore drills and restores that stop your services say what they're about to do first.
- While the sample data loads, the first-run page now says which admin asked for it, for example "Asked by Sam." With two admins on one server, the page no longer leaves you wondering who started it. A load that the install started says "Loaded during setup." instead. If the page doesn't know who asked, it says nothing, and it never shows an email address. A page that's already open shows the line without a reload.
- On a Mac, the app can now update Moorhold itself. When your copy of the app carries a newer release than the one running on your Mac, the button in the title bar says it is ready, and Update now starts it. The new release checks your Mac with its own checks, takes a backup of every database first unless you have turned backups off, and restarts Moorhold. The window lists each step, and quitting waits until the update has finished. If the update can't go ahead, the app shows the reason in full. If it fails part way, the earlier release runs again. A release that has steps for you to do is updated from the Updates page instead, which lists them. Afterwards the Updates page and the audit log say the update was started in the app, and by which account on your Mac.
- On a Mac, the first setup screen now asks whether to load the sample dashboard, and the box is already ticked. If you leave it ticked, the install sets up the sample and starts loading it, so you don't have to ask for it afterwards. It is your choice: untick the box to start with Moorhold empty. You can change it until the install begins. If you leave it out, you can add it later from the launchpad.
- The Mac app now keeps a small log of setup on your Mac, with the time of each step. It is the file setup-log.txt in the app's folder in Application Support, and it helps to explain a setup that is slow or stops. Before a line is written, the app takes out your setup code and anything that looks like a password or key. Nothing is written before you accept the terms. The log stays on your Mac and is kept small, and removing Moorhold deletes it.
- The Mac app now shows Moorhold's terms before it sets anything up. The screen links the full terms at moorhold.dev/terms and shows their sanctions line, and setup starts only when you accept. If you don't accept, nothing is set up. A Mac that already has Moorhold asks once, the next time you open the app after updating it. If you don't accept there, Moorhold doesn't start and your data stays on your Mac. When the terms change, the app asks again once it has been updated.
- Commands that start, stop or change your Moorhold server now run one at a time. If you run one while another is still going, for example straight after a restart, it says which command it's waiting for and goes on when that one ends. A command you run waits up to 30 minutes, then stops and names the command that's still running. The start at boot waits 6 minutes, and a tool waking from sleep and the stop at shutdown wait one minute. An automatic update that can't get its turn in 30 minutes is refused with nothing changed, and automatic updates aren't paused.
- Waits in the portal now show what is happening and update themselves, so you don't have to reload the page or choose Check again. A source's load, saving a source and "Update the tools now" show their steps and how far they've got. Step 2 of the first pipeline waits for its table by itself, and a memory request that the server is acting on shows its steps on the home page. A catalog search made while DataHub is asleep waits, and runs once DataHub is awake. The setup page notices when the sample data has been added.
- Automatic updates and off-site backups are free on every server, including one with no access key. An admin can turn on "Install updates automatically" on the Updates page, and
sudo moorhold backup target s3sends the backups to an S3 bucket of your own. - One admin is now enough for an update, however many admins the server has. On the Updates page, the admin who asks for an update approves it themselves by typing the version. An update that was asked for and approved on an earlier release, under that release's rules, is still installed. When
sudo moorhold upgrademoves a tool to a new version, the person at the terminal approves it by typing each tool's name, and the audit log and upgrades.log name the account that ran sudo.
Changed #
- The old update units are removed. The update from 2026.11.3 removes moorhold-update.path and moorhold-update.service, and the folder the old update doorbell used, and says so. An update from 2026.11.2 or earlier leaves them in place, so a rollback still has its doorbell, and the next update removes them. Approved updates are started by moorhold-requests.service, and moorhold-update.timer keeps its name. If something stops it removing them, it says what, and the next update tries again.
Fixed #
- If you approve an update in the portal while an update you started on the server with
sudo moorhold upgradeis still running, Moorhold now checks and installs the approved one once yours has finished. Before, it waited for the next approval or the next maintenance window. - The audit page now says who asked for a change to the server, such as adding the sample data, and who approved it. A request the server carries out shows two rows, and each now says whether it's the start or the end.
- When a download, an update or an apply fails, the reason Moorhold shows, and the one it records, now hide a password or key even when its setting's name only ends in one, such as POSTGRES_PASSWORD or SUPERSET_SECRET_KEY. Moorhold's own generated secrets are hidden by name too, and a cache key or an Airflow setting's name stays readable.
- When you take a tool out of a source's settings, Moorhold now removes what it had made in that tool (a Trino catalog, say) and forgets the link to it. If it can't remove it now, because the tool is asleep or something still depends on it, the source page says what's left behind. Deleting a source tears those leftovers down too. If a tool is asleep or unhealthy, the delete waits for it.
- If Moorhold fails to start when the server boots, it now waits 15 seconds and tries once more. A start by hand isn't tried again. Every start keeps a short record, and
moorhold statussays if the last one failed, which services didn't come up, and to runsudo moorhold start. The Launchpad shows the same to an administrator, until a start works. A start that needed two tries is shown for a week. A start that stops with an error before Docker answers, such as a secret that can't be read, is recorded as failed too, though it isn't tried again. The upgrade also rewrites the boot unit so systemd allows a start 70 minutes: enough for both tries. - After you open the sample dashboard from the last step of setup, coming back now takes you to the launchpad. Before, the setup page was shown again and you had to press "Do this later" to leave it. If the sample is still loading, or its load has failed, the setup page stays, so that you can watch it or try again.
- On a Mac, if Moorhold's private space fails to start and Moorhold can't tell whether it holds your work, Moorhold now leaves it alone instead of deleting it, and says what to do: try again, restart the Mac, ask for support, or delete it on purpose. A first setup that fails on its first start still clears itself and starts again.
- On a Mac with no internet connection, first setup now says so before it makes anything: "Moorhold needs the internet for its first setup, and this Mac doesn't seem to be connected. Connect to the internet, then press Try again." Before, it said only that it couldn't create the virtual machine, and it left a part-made one behind. If the connection drops while the Linux system downloads, Moorhold now clears what the download left, so that "Try again" starts cleanly.
- On a Mac, the first start of the Linux system no longer waits two minutes for a network interface that never comes up.
- On a Mac, the first setup screen now says "Downloading the Linux system Moorhold runs on" while that download is happening, and "Creating a private space for Moorhold on this Mac" while the private space starts for the first time. Before, the two were the other way round: the screen said it was creating the private space for the whole of the download.
- By default, robots.txt on the portal and on published tools now puts "User-agent: *" and "Disallow: /" on lines of their own, so crawlers that follow robots.txt can read the rule. In 2026.11.3 it came out as a single line, so it held no rule crawlers could use.
- Moorhold now sets up the sample dashboard once the sample data has loaded, without waiting for Moorhold's regular five-minute check. On a Mac, the dashboard could appear up to about 10 minutes after the sample data had loaded.
- Adding the sample data straight after removing it now works. While Airflow is still clearing out the old load job, the add waits and says so, instead of failing with a 404 error.
- If you search the catalog while signed out and then sign in, you come back to your search with its term still in place, rather than to an empty Assets page.
- The source form now tells you what to type. A problem in Resources or Checks names the keys that are wanted, where it used to name only the ones it rejects. Each field shows a hint and an example, and each credentials section on the database form says when it's needed.
- If your server restarts while it's installing an update, Moorhold now records whether the update finished once Moorhold is running again. Before, the update stayed installing until the next approval or the next maintenance window. A restart while the update is still being checked or downloaded leaves it approved, and it installs at the next approval or maintenance window.
- From this release on, the disk space check before an update counts the images the update would download for your own setup, and the images of any tool it adds. If it can't work that out, it counts every image, as before. It used to count every image in the new release, including ones for tools your setup leaves out, so a Mac with enough room could be told there wasn't enough. If space really is short on a Mac, the message now says that the space is inside Moorhold's private space, so freeing space on the Mac won't help, and how to get help. When an update approved in the portal stops at these checks, the Updates page now shows the whole refusal, not only its first line (a long one is cut).
Verified #
- Unit and golden tests: pass, on the release pull request's own check run.
- Images: each of Moorhold's 12 images was built for x86_64 and for ARM and published as one image that holds both, in the images run this release's manifest was made from. Every image passed the licence check on both platforms in that run, and every image our test server runs is one the manifest names.
- On our test server: a full server on 2026.11.3 was updated to 2026.11.4 with the published installer. It took a rollback point first, and the restore drill passed after the update.
- A restart on our test server: after a reboot on 2026.11.4, Moorhold started at boot and ran to "Moorhold is running" on the first try, with nothing run by hand, and all 26 services were healthy.
- 300 restarts: a full server with 12 GB of memory, updated from 2026.11.3 to 2026.11.4, was restarted 300 times in a row. Every restart ended with Moorhold running and healthy. 287 started on the first try, and 13 on the second try, 15 seconds after the first had failed (see Still known).
- Commands one at a time: on another server running this release,
moorhold applyrun whilemoorhold startwas still going said it was waiting formoorhold start, and went on once the start had ended. Ten times, a command run as soon as the server answered after a restart either waited for the start at boot or was waited for, and every one finished. An update started while another command was still running waited 30 minutes, then stopped with "Not installed" and nothing changed. - On a Mac: on a real Mac running 2026.11.3, the Moorhold app updated itself from the live update feed, showed the terms, then said that Moorhold 2026.11.4 was ready. Update now took Moorhold from 2026.11.3 to 2026.11.4 end to end in about four and a half minutes. It checked the signed release, took a rollback point and restarted Moorhold, and the restore drill passed afterwards.
- In the code and its tests: each sentence under New and Fixed carries a claim that the release notes check reads from the code. The Changed item and the Updating paragraphs are read from the code and from 2026.11.3's published notes, not checked by that job.
- Owed: the first update installed by moorhold-requests.service, an update from 2026.11.3 to this release approved in the portal. A server that still fails to start after its second try at boot. A server restarted during an update install, settled afterwards. An admin approving an update while
sudo moorhold upgradeis running. One admin asking for an update and approving it on a server with two admins. A tool dropped from a source on a server, with its catalog removed. How a server records an automatic update refused after 30 minutes, and automatic updates staying on after it. An update from the Moorhold app on a Mac that fails part way, and what the Updates page and the audit log say after an update from the app. The first setup of the Moorhold app for Mac with its terms, its sample box and its network check. The first start of the Linux system on a Mac without the two-minute wait. The Mac app's setup log, on a Mac. Also still owed from 2026.11.3: automatic updates on a server, and a moorhold-update.timer masked before the update. An install of this release on a 12 GB server with the full profile or a 6 GB one with core, and the light profile in 4 GB. Adding the lake to an installed server. The wait for a busy download server, on a server and in the Moorhold app for Mac. The Lineage menu on a Stack without DataHub, and the sample dashboard's Month column in the Moorhold app for Mac. Also still owed from 2026.11.2: the Updates page offering a release once it's the latest, the update window on a whole update, and the message behind a proxy that refuses get.moorhold.dev. So are the updates from releases before 2026.10.16, a fresh install with the sample data, a daily backup on a server that holds kept copies, and a restore drill with a kept copy of a long name.
Images #
Every one of Moorhold's own images is rebuilt from this release's source, for x86_64 and ARM, and all 12 have new digests. No tool changes version, and the images Moorhold takes from upstream keep the digests they had in 2026.11.3.
Still known #
- A start after a restart can take about a minute longer. In our tests, about one start in 23 after a server restart needed its second try, because the query engine (Trino) restarted once during the start. Moorhold tries again by itself, and nothing needs doing. We plan to fix this in a later release.
- A web service source after a restart. After a server restart, a web service source added in the portal may not load until
sudo moorhold startis run once, because Moorhold starts without that source's credentials. If you have such a source, runsudo moorhold startonce after each restart. We plan to fix this in a later release. - An interrupted load can leave a table empty. If a web service source's load is cut off part way, for example by a restart, an update or running out of memory, its tables whose
writeModeisreplacecan be left empty until the next load that finishes. Dashboards built on them show no rows until then. Nothing is lost: the next load fills them again, so there's nothing to do. Tables whosewriteModeismergeorappendkeep their rows. We plan to fix this in a later release. - Schemas named
crmandcrm_staging. Don't give a web service source a schema named after another web service source's schema with_stagingon the end, such ascrmandcrm_staging. If both have a table of the same name, a load of the first can replace that table's rows in the second with its own. We plan to fix this in a later release. - Many people behind one address. The server limits how often one address can load the first-run pages. If many people reach Moorhold from one address, or someone keeps mistyping a password, an open first-run page can still be refused and show a blank page. Wait a minute, then reload it.
- A source that runs the sample's own code. Removing the sample also removes its code, so while the sample is removed, a source that runs the sample's code is refused until the sample is added back. We've seen this only with a test source on our test server.
- ARM servers. Moorhold servers still need an x86_64 (amd64) processor. ARM is for the Moorhold app for Mac only. An install on a real ARM machine is owed.
- The Moorhold app for Mac is early access. A first setup from its disk image is owed on a Mac.
- A Mac with 8 GB of memory. The Moorhold app for Mac needs 16 GB of memory and checks for it before setup.
- Removing Moorhold from a Mac. The removal has been tested on throwaway folders only, not on a Mac with Moorhold installed. Lima's cached Linux image stays after a removal, and the app names it. If ~/.moorhold, or a folder above it, is a link, removal stops and removes nothing, and the window says what to do.
- 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
readersor under its row-level rule. An agent can run them only on a mart with a row-level rule. - Metrics on the native Assets page. The page says it lists metrics, but no metric appears on it.
- Lineage on a Stack without DataHub. The portal reads lineage from DataHub, so on a Stack without DataHub no page shows lineage. 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 on a small server. On a full server with less than about 24 GB of memory (the 12 GB and 16 GB sizes included), or a core server with 8 GB, more memory for a tool is refused: the portal says the server hasn't room, because Moorhold keeps 4.5 GiB spare above its apps' limits.
- 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.
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
To install this release on a new server, see Install on a server.
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.
| File | SHA-256 |
|---|---|
| moorhold-2026.11.4.tar.gz | 5a239dd49523f8974e9bbbe1a481b6e942f77a3b96e7c51aaef9af982ef86081 |
| manifest.yaml | 4f403c7c071e4559a7c05d73baa2114db015bfff6c2c8d04fb9a0910e5df909c |
| release.lock | f4532cbf64d6677ce23ddefca66d6df0c592dbf5fe19c270412a41bc461736ab |
| install.sh | 31575b713ddee80dd36de3e5f1bb5e93da36a34f066ba145212ed37bf4ec6618 |
| cloud-init-ionos.yaml | 8c0d5dffea2a370a7728f392f353fbd9b960d005e271ac910a40b60b28cf1aa2 |
| cloud-init-hetzner.yaml | fc371583a6a8c4d57b33f206a284310f7642abf7793088319c19eec3947e9b6f |
| Moorhold-2026.11.4.dmg | 78156e24f8cc20fe3e9da19d4fc0874528b5aad31a2e456068663c7841fd5e38 |
| release.lock.minisig | Signature, key 7F6D12F3F6217F9C |
| SHA256SUMS | The checksums above |
minisign -Vm release.lock -p moorhold-release.pub sha256sum -c SHA256SUMS
The Mac disk image is signed and notarised. It isn't in release.lock or SHA256SUMS: check it against the SHA-256 in its row.
Public key: get.moorhold.dev/moorhold-release.pub