Release state
Replaced #
This was the Latest release until 2026.10.16 replaced it. Before it became Latest, we updated our own Moorhold server to it from 2026.10.13, 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 updates the portal's web framework and a library Moorhold uses to versions that fix published security advisories. The portal and an agent's replies now call a source a "Postgres database" or a "web service". The portal says Moorhold where it said the reconciler. A tool that is waiting for a source's first load reads Waiting instead of Ready. A data engineer can start a web service's first load on a server whose Stack lists its groups with spaces inside the brackets, once the server has this update, and the update from 2026.10.10 no longer prints an error. A local preview of Moorhold for the Mac is in this release's source. It isn't public, and there's no download. Edited 9 November 2026: the paid plan named under Owed was withdrawn before sale, so its name was removed.
https://moorhold.dev/releases/2026.10.14Before you update #
- What changes
- A tool that is waiting for a source's first load now reads Waiting instead of Ready, and the portal and an agent's replies use plain names for sources. After the update, data engineers can start a web service's first load on more servers. The portal's web framework and a library Moorhold uses are updated for published security advisories. Moorhold for the Mac is a local preview that isn't public.
- 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 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.13. On 2026.10.12 or 2026.10.11, if DataHub or Superset is asleep, open it just before you run sudo moorhold upgrade or ask for the update on the Updates page, or the update refuses to start: see Updating. If you're updating from a release before 2026.10.13, also read 2026.10.13's Updating: a web service in your Stack file whose secret reference isn't a file directly in /etc/moorhold/secrets named in capital letters, digits and underscores stops the update until you rename or move it, and a script of yours that runs sudo moorhold users reset-password needs --no-temporary if the person should keep the password it sets. From 2026.10.10, see also 2026.10.11's Updating for the sample data.
- Still to be tested
- This release hasn't been through its test servers: the update from 2026.10.13, 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 are the updates from earlier releases and the Updates page offering 2026.10.14 once it's the latest release. The latest build of the Mac app hasn't been tried on a Mac.
Updating #
On a server running 2026.10.13, 2026.10.12 or 2026.10.10, update from the server's command line with:
sudo moorhold upgrade 2026.10.14
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 2026.10.12 or 2026.10.11, wake any tool that's asleep before you update this way. sudo moorhold upgrade and the Updates page both run the checks of the release you're updating from, which count a sleeping tool's stopped services as failed on 2026.10.12 and 2026.10.11, so the update refuses to start and changes nothing. Open each sleeping tool in your browser just before you update, and start the update straight away. The installer below runs this release's checks, so it updates a server while a tool sleeps. A server on 2026.10.13 needs none of this.
On a server running 2026.10.13, 2026.10.12 or 2026.10.10, 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.14/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.
A server on 2026.10.11, which was published but never the latest release, updates the same ways. Read 2026.10.12's notes as well: they fix a security problem in 2026.10.11's mail settings, and say what to do if the Mail page then shows "Moorhold isn't using the saved mail settings."
If you're updating from a release before 2026.10.13, read 2026.10.13's Updating as well. It says how a web service's secret has to be named and what sudo moorhold users reset-password does now, and it names the two new secrets. If you're updating from 2026.10.10, 2026.10.11's Updating says what else that update changes, the sample data among them.
What else this update changes:
- Who may start a first load. If your Stack has no
firstLoadGroupsline and the groups that may propose and approve changes are the ones the installer wrote, the update addsfirstLoadGroups: [data-engineers, shipboard-admins]underspec.agents, just afterapproverGroups, with a comment above it. It now does so when those groups are written with spaces inside the brackets, such as[ data-engineers, shipboard-admins ], and it keeps the spacing you use. It leaves the Stack alone if you've changed the groups that may propose or approve changes, or if the Stack namesfirstLoadGroupsalready, even in a comment. A 2026.10.13 Stack where you took the line out after 2026.10.13 added it is left alone too. See Fixed.
New #
- A local preview of Moorhold for the Mac. Moorhold.app runs Moorhold for one person on one Mac, inside a virtual machine that only the Mac can reach. Nothing in it listens on the network, and no folder of the Mac is shared with it. It's a preview of this release's source, built on a Mac. There's no download, and the app isn't part of the signed release. It needs an Apple silicon Mac with macOS 14 or later, 16 GB of memory and 30 GB of free disk space, and says in plain sentences when a Mac falls short. It stops the virtual machine when you quit and starts it again when you open the app. Behind it are a lighter Stack, which runs Postgres, Airflow, Superset, Keycloak and the portal without Trino or DataHub, and a local mode for the installer. Both are in this release's installer and command line, which accept
--local, but only the Mac app has been tried with them. A server that's already installed refuses both, and a local install can't become a server. Installing and updating a server work as they did. - Plain names for sources. The proposals list and a proposal's page say "create the Postgres database
ops" or "create the web servicesupplier", with "Requested web service specification" for what was asked. The Stack page and the Sources pages say Moorhold where they said the reconciler, and so do the messages after you approve or withdraw a change. The Stack page's button is now "Update the tools now". When Moorhold is already updating the tools, the Stack page says it has taken the pass over and lists what is still being set up in the tools and what is still being removed from them. When nothing is left, it says the tools are up to date. A source's delete step starts with "The data in the source itself is never touched.", then says what a soft delete removes and keeps, and what a hard delete also deletes for good. - For agents using the portal's MCP server. A proposal's
targetinget_proposalandlist_proposalsis now text for people to read, such as "web service supplier", where it wasRestSource/supplier. A proposal for something that isn't a source, such as an upgrade of a tool, keeps its form, such asComponent/trino. Refer to a proposal by itsproposalfield, not by itstarget.
Fixed #
- Security updates. The portal's web framework, Next.js, moves from 16.3.7 to 16.4.3, and the zod library Moorhold uses to check input moves from 4.6.5 to 4.6.7. Both versions fix published security advisories. source-map-js, a library the framework's CSS build uses, moves to 1.2.2 for an advisory of its own.
npm auditon the release's production packages reports no known vulnerabilities. - A tool that is waiting reads Waiting. When a web service is applied before its first load, Superset can't make the source's datasets, because their tables don't exist until the load has written them. The Sources list and the source's page used to read Ready for Superset all that time. They now read Waiting, and name each dataset it is waiting for. Moorhold makes them on its next regular check, or when Superset wakes if your server lets it sleep, and the tool then reads Ready. A check that skips a sleeping tool no longer forgets what that tool is waiting for.
- Starting a first load after the update. On a server whose Stack lists its groups with spaces inside the brackets, the update in 2026.10.13 left out
firstLoadGroups, so only admins saw "Start first load" on a web service's page, although the notes said data engineers could start one. This update adds the line, as Updating says. The last release's notes listed this as still known. - An error printed during the update from 2026.10.10. The update used to print an error ending "Unknown option '--kind'", then "Couldn't read the store's sources", because the release it was updating from couldn't list the portal's sources that way. It now asks that release another way and prints neither line. A web service added in the portal whose secret is a file directly in
/etc/moorhold/secretsgets its secret in the same update, with nosudo moorhold applyafterwards. If the file isn't there, the update prints a line saying it skipped that web service, andsudo moorhold applygives it the secret once the file is. If both ways fail, it still prints the second line once and carries on. The last release's notes listed this as still known. - The first-run page while the sample loads. While the sample dashboard is being made, the page checks on it by itself and says what it's doing. It moves on to the choice when the load has finished. "Check again" is still there. Where the sample wasn't added at install, the page now offers it as an option beside connecting your own data, with the command to run on a server. In the Mac preview, which has no Trino, the first pipeline's steps send you to Superset's SQL Lab, which reads the warehouse directly. On an installed server the first-run card still offers a web service only.
- Setup pages after you sign in. About five minutes after you signed in, the setup pages used to say "Sign in to carry on". They now renew your session and carry on. A setup page left open from before setup finished, with a choice still on it, now takes the local admin to the portal and no longer shows an error.
Verified #
- Unit and golden tests: pass.
- Images: every image passed the licence check, and each image is the one the manifest names. No tool changes version, and every image from upstream keeps its 2026.10.13 digest. Every one of Moorhold's own images is new.
- Security updates:
npm auditon the release's production packages reports no known vulnerabilities. - On the test servers: the update from 2026.10.13 on the long-running test server, which runs the full profile, ended on 2026.10.14, took its rollback point, kept the server's settings and data, and passed the restore drill afterwards, with every service healthy and nothing done by hand. The images it runs are the ones this release names. On an installed server, Add source offers a web service only. The signing drill passed.
- In the code and its tests: the Waiting state and what keeps it through a pass that skips a sleeping tool, the plain names on the pages and in the portal's MCP server, the update's
firstLoadGroupsline for each way the groups can be written, the update from a release that can't list the store's sources, and the first-run page's checking. - On a Mac: an earlier build of the Mac app, signed and notarised by Apple, ran on an Apple silicon Mac: installed from a quarantined disk image, a first run, quit and reopen, a restart of the Mac, removal and a reinstall, with everything listening only on the Mac's own address. This release's final build hasn't been tried on a Mac.
- Owed: the update from releases before 2026.10.13, a rollback after the update, a fresh install with the sample data, Waiting on a real source, the
firstLoadGroupsline on a server whose groups have spaces, a data engineer starting a first load, the first-run page checking by itself on a new server, the setup pages renewing a session after five minutes, and the plain names in an agent's replies. The paid plan, its grace period and recovery are checked against a test account service from the next release. The Updates page offering 2026.10.14 once it's Latest is checked after that.
Images #
Every one of Moorhold's own images is rebuilt from this release's source.
Still known #
- 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.
- The sample data card on a server. On a server, the sample data card on the first-run page shows a "Download the sample data" button that does nothing there; use the
sudo moorhold sample-data addcommand it shows. - 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.
| File | SHA-256 |
|---|---|
| moorhold-2026.10.14.tar.gz | a00329537f64e585416f6c62b9fb3bf54b23f7b061fb34578655664103fc4cd8 |
| manifest.yaml | 21d6c71fd0d70f1ff4c14826ce3351b917cb5be591dd5a6ed9f70657d19c35b0 |
| release.lock | b29762fa168dc82cfdc1630c3f1397484b1de63bc5d5b4ac809a419b3cb6b451 |
| install.sh | 39fff94eec5aec3ee38a661a67dde8253c1933d5691e0e585c2fde78145ed23a |
| cloud-init-ionos.yaml | 57363360b80094ed8c0a331686db7ac48f17076d0ed537ee4d468f73bbf3c17e |
| cloud-init-hetzner.yaml | 5d9f06f361fa53e274957fb66e436db1d38afd5c066aef28eaa4971cb47cb896 |
| release.lock.minisig | Signature, key 7F6D12F3F6217F9C |
| SHA256SUMS | The checksums above |
minisign -Vm release.lock -p moorhold-release.pub sha256sum -c SHA256SUMS
Public key: get.moorhold.dev/moorhold-release.pub