Release notes
Moorhold Data
Release notes
Every Moorhold release, newest first. Each page starts with what changes and what to know before you update. Moorhold is in early access, so we say plainly what we haven't tested yet. Questions about a release? Email hello@moorhold.dev.
Latest is the release we recommend. A release becomes Latest after it has run on our own Moorhold server and passed a restore drill there. Newer releases are listed above it until then, and some of them are skipped.
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.
To update a server, use the Latest release, 2026.11.4. The 2026.11.4 release notes say which releases it updates in place, and how.
If your server runs a release they don't mention, email hello@moorhold.dev and we'll help. Tell us which version you're on. Please don't send passwords or keys.
To see which version your server runs, run this on it:
readlink /opt/moorhold/current
It prints /opt/moorhold/releases/<version>.
Setting up a new server instead? Follow Install on a server, which installs the Latest release.
Current release, to install or check by hand: get.moorhold.dev
Latest version, for scripts: get.moorhold.dev/LATEST · Release feed: /releases/feed.xml
All releases #
- Latest
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.
- Replaced
The installer accepts smaller servers, sized from measuring what each profile uses: 12 GB for full and 6 GB for core, and 4 GB for light in local mode. Updates approved in the portal, and automatic updates, are now installed by the same service as the other things an admin approves. Servers tell search engines not to index the portal or published tools. Installs and updates wait and try again when the download server is busy, starting Moorhold after a restart no longer stops part-way, and adding the lake to a server gets two fixes.
- Replaced
Moorhold's own images are now built for ARM (arm64) as well as x86_64, and the release carries Node for both, which the Moorhold app for Mac needs to install a signed release. One admin is now enough to add the sample data or give a tool more memory. The first-run page follows the sample load to the end, and adding the sample starts one load. The Moorhold app for Mac goes public as early access once 2026.11.2 is the latest release. It replaces 2026.11.1, which wasn't published.
- Replaced
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.
- Replaced
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.
- Replaced
Automatic updates in a maintenance window and off-site backups to a bucket of your own were to come with a paid plan, since withdrawn. A server whose backups are in a bucket can be brought back onto a new one. An admin can set the mail password on the Mail page, and a data engineer can start a web service's first load from its page. Resetting a password now makes the person choose a new one when they sign in.
- Replaced Security fix
A security fix for the mail settings that 2026.10.11 brought in: the mail server's password reference now takes only the password set with sudo moorhold mail password, or another smtp- file beside it. Everything else is as in 2026.10.11.
- Skipped
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.
- Replaced
Trino's tables now show in DataHub. An admin can ask for more memory for an app from the portal, a rollback no longer stops halfway when you've dropped a kept copy, and a restore from the wrong snapshot is refused before anything stops.
- Replaced
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.
- Replaced
A fresh install now checks the server before it asks for your access key, and the launchpad shows which release you run. Moorhold now stops cleanly when the server shuts down, so its services start in order after a reboot.
- Replaced
Signing out of any tool now signs you out of the Moorhold portal too, and every update makes sure Moorhold starts again after a reboot. Admins can reset a portal password from the server and choose to hear about new releases.
- Skipped
Servers running 2026.10.4 or 2026.10.5 can now update in place, with backups on by default and a rollback point taken before the update. Signing out of one tool now signs you out of the others.
A server updated to it may not start Moorhold again by itself after a reboot. 2026.10.7 fixes that. If your server runs 2026.10.4 or 2026.10.5, don't use the 2026.10.6 update steps. What to do if your server runs 2026.10.6
- Replaced
Ships the Moorhold sample: AI Release Radar dashboard and loads the sample by default on new installs. There's no in-place upgrade from 2026.10.4.
- Replaced
Adds a network check to the installer and an optional relay for home networks. The relay hasn't been tried on a real cloud server yet.
- Replaced
Fixes an install failure on servers that can't reach their own public address, and the installer now always says what to do next.
- Replaced
Fixes file permissions, sign-in between the tools, Trino restarts and signing in after the setup wizard. Not yet re-tested with a full install.
- Replaced Early build
Early build, released before we published detailed release notes.
- Replaced Early build
Early build, released before we published detailed release notes.