Release notes / 2026.11.2

Early access release

Moorhold 2026.11.2 Replaced

Published

Release state

Replaced #

This was the Latest release until 2026.11.3 replaced it. Before it became Latest, we updated our own Moorhold server to it from 2026.10.16, 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.11.1, which wasn't published. 2026.11.1 was skipped because the first-run page didn't follow the sample load on our test server, and adding the sample started two loads. 2026.11.2 has everything 2026.11.1 was going to bring, with those fixed and a few more fixes made since. New, Changed and Fixed describe it as it now works. This release prepares Moorhold for the Mac and tidies up the installer and the first-run page. Moorhold's own images are now built for ARM (arm64) processors as well as x86_64, and the signed release carries Node for both, so the Moorhold app for Mac can install a signed release instead of building one on the Mac. A server is unchanged by this: Moorhold servers still need x86_64, and the installer now says so as soon as it has checked the release's signature. On a server, one admin is now enough to add the sample data or give a tool more memory. The first-run page says the sample load takes about 15 minutes, the longest a load took on our test server, and a first-run page left open follows the load to the end. The Node that Moorhold ships is now 22.23.4, a security release. The Moorhold app for Mac goes public as early access when 2026.11.2 becomes the latest release. Its disk image is published on get.moorhold.dev/mac then, separately from this release's signed files.

https://moorhold.dev/releases/2026.11.2

Before you update #

What changes
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.
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.10.16. If you're updating from an earlier release, read 2026.10.16's Updating first, and the Updating of any release between.
Still to be tested
Owed: the Updates page offering 2026.11.2 once it's the latest release, the update window on a whole update, and this release's message behind a proxy that refuses get.moorhold.dev. Also owed: 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, a restore drill with a kept copy of a long name, an install on a real ARM machine, and the Moorhold app for Mac on a Mac.

Updating #

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

sudo moorhold upgrade 2026.11.2

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. This is the first update that 2026.10.16's progress window follows from start to end: it names each step as the server reaches it, holds the portal while Moorhold restarts, and shows the result when the portal answers again.

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.2/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.16, read 2026.10.16's Updating as well, and the Updating of any release between.

What else this update changes:

  • Moorhold's images. Every one of Moorhold's own images is rebuilt from this release's source, and each now holds an x86_64 build and an ARM build. A server pulls the x86_64 one, as before.
  • The release's Node. The release's own Node moves from 22.23.3 to 22.23.4.

New #

  • ARM builds of Moorhold's images. Each of Moorhold's own images is built on an x86_64 machine and on an ARM machine, and published as one image that holds both. An image is published only once both builds and their licence checks have passed.
  • Node for ARM in the release. The signed release now names Node for ARM (aarch64) as well as for x86_64. The release is made only if each download matches the checksum recorded for it in Moorhold's source.
  • The Moorhold app for Mac installs a signed release. In the Moorhold app for Mac, first setup now installs the signed release the app was built for, with the same checks as a server: the release's installer checks the release's signature and pulls each image by its digest. Nothing is built on the Mac. It needs a Mac with Apple silicon and 16 GB of memory.
  • The Moorhold app for Mac goes public. It's early access. Once 2026.11.2 is the latest release, download Moorhold-2026.11.2.dmg from get.moorhold.dev/mac, open it and drag Moorhold to Applications. The disk image is signed with Allotment Technology Ltd's Developer ID and notarised by Apple. It carries this release's installer and release lock, and no source. The app needs a Mac with Apple silicon, macOS 14 or later, 16 GB of memory and 30 GB of free disk, and says what a Mac lacks. It runs Moorhold in a virtual machine on the Mac and needs no access key.
  • A local install needs no access key. install.sh --local, moorhold install --local and sudo moorhold upgrade on a local install now go ahead without an access key, and use one only if you give one or one is already kept. sudo moorhold status says "Access key: none needed. A local install pulls without one." A server still needs its access key, as before.
  • Removing Moorhold from a Mac. The Moorhold app for Mac has "Remove Moorhold from this Mac…" in its File menu. It says what it deletes and what it keeps, and goes ahead only after you tick a box. It then deletes Moorhold's virtual machine and its data, the saved sign-in and the app's own folders, and leaves the app itself. If setup fails because the Mac already holds another release, the failure screen offers "Remove and start again…".
  • Support details on a Mac. The app's Help menu has "Moorhold support…", with the address to write to and the details to send: the app and release versions, the machine's state and, after a failed setup, its last lines, with credentials, addresses and other people's folders taken out. The app sends nothing itself.

Changed #

  • One admin is enough for the sample data and for more memory. On a server, when an admin presses "Download the sample data" on the first-run page, or asks to give a tool more memory, the request is approved as they ask, and the server does it when it's due. Another admin no longer has to approve it, however many admins there are. The audit log records "Asked for and approved by" and the admin's name, but the portal's audit page doesn't show it: see Still known. A request made before the update that's still waiting can be approved by any admin, including the one who asked. When the server acts on a request, it refuses one approved by someone who's no longer an admin. Updates and Proposals keep their own approval rules.
  • How long the sample data takes. On a server, the first-run page and the installer now say the sample load takes about 15 minutes. On our test server, from approval to loaded, one load took about that long and others took between 5.5 and 7.6 minutes. sudo moorhold sample-data add now gives that time too when the load starts, and no longer says it can take up to 10 minutes. In the Moorhold app for Mac, the sample messages say about 2 minutes, from runs on one Apple silicon Mac. Where the page can't tell a Mac from a server, it gives both. The sample's card now says adding it restarts Airflow's scheduler.
  • A preview build on the Updates page. In the Moorhold app for Mac, a developer's preview build can now be updated to a signed release that's newer than the release it was built from. On a server nothing changes.

Fixed #

  • The first-run page during the sample load. With two admins' first-run pages open during the sample load, the pages checked so often that the server started refusing them, one page went white, and neither followed the load to the end. The page now asks for itself again only when something has changed, and not more than once every 20 seconds. If the server asks it to slow down, it waits and says "Still working. This page is checking less often, and it'll catch up by itself." An answer it can't read leaves the page as it is. While nothing is running, an open page also notices a new request for the sample data, or the sample being removed, without a reload, for about an hour. After about an hour and a half without an end to the load, the page stops checking and asks you to open it again.
  • A first-run page left open stopped following the sample load. While the sample was being added, or when Airflow couldn't be read for a moment, an open first-run page could stop checking and show "Load it now" part-way through. It now keeps checking until the load ends. A "Load it now", "Try again" or "Run it again" pressed on a page that's out of date starts nothing while a load is queued or running, and takes you back to the first-run page. If Moorhold can't see whether a load is running, it starts nothing and says "Moorhold can't see whether a load is already running. Try again in a moment."
  • Adding the sample started two loads. sudo moorhold sample-data add, the installer with the sample, and the first-run page's "Download the sample data" each started the sample's load twice, once by Airflow's scheduler and once by Moorhold. They now start it once: Moorhold waits up to a minute for the scheduler's run, and starts one itself only if none appears. While it waits it says "Waiting for Airflow's scheduler to start a run."
  • Removing the sample deleted a password another source used. sudo moorhold sample-data remove deleted the sample's password file even when another source in your Stack used it, so that source could no longer be set up. It now keeps the file while another source uses it, and says so, for example "Kept its password: RestSource/bench-first-load still uses it." If it can't tell, it keeps the file and prints the command to delete it.
  • A download through a proxy that refuses it. Once a server runs this release, when sudo moorhold upgrade and its checks go through a proxy that refuses the connection to get.moorhold.dev, they say "a proxy refused the connection to get.moorhold.dev (it answered 403). This server is set to use one (HTTPS_PROXY), and it may not allow that address", instead of "fetch failed". They never show the proxy's address or credentials. If a connection ends part-way through a download, the command says so and asks you to try again. Before, it could stop with an error from inside Node. A download that stops part-way leaves no partial file behind. The update to this release is checked by 2026.10.16's command, which still says "fetch failed" behind such a proxy.
  • The update window with backups off. On a server with backups off, the update takes no rollback point, but the window listed "Taking the rollback point" and ticked it. Once a server runs this release, the window leaves out that step and the backup restore check when backups are off. On the update to this release, the window lists it until Moorhold restarts.
  • Piping a command that changes the server. A rollback or an update run into head or another command that stops reading early could be stopped half done. With this release's moorhold, the work carries on to the end when the reader goes. The update to this release starts in 2026.10.16's command, so don't pipe that one.
  • The rollback point and kept copies. The rollback point taken before an update no longer backs up the copies an earlier rollback kept. Once a server runs this release, the update's disk space check doesn't count them either. On the update to this release, sudo moorhold upgrade and the Updates page still count them in their space check, and the installer doesn't. A rollback doesn't restore them, so they only took space. Daily backups and the restore drill still include them.
  • The installer on an ARM server. The installer now stops on an ARM (aarch64) server as soon as it has checked the release's signature, before it installs any of Moorhold, and says: "this server has an ARM (aarch64) processor: Moorhold servers need x86_64. ARM is for local mode on a Mac (--local)". sudo moorhold upgrade refuses an ARM server too. Local mode on a Mac is not affected.
  • sudo moorhold sample-data add on a core server. With no --profile, it now adds only what the installed profile runs, as the first-run page does. If it can't tell the installed profile, add and remove stop and ask you to give --profile, instead of assuming the full profile. On a server where the first-run page has the "Download the sample data" button, the first pipeline's lesson now points an admin to that button, and tells anyone else to ask an admin.

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. Every image passed the licence check on both platforms, and our test server runs the images the manifest names.
  • The signing drill: a restore drill of 2026.11.2's images passed on the release commit, on the core profile.
  • On our test server: the update from 2026.10.16 by the installer took a rollback point first and ended with all 26 services healthy, and the restore drill passed after it. The server kept its data and settings. Its Node prints v22.23.4, and the release lock names Node 22.23.4 for x86_64 and for ARM. The Updates page says "This server runs Moorhold 2026.11.2." and nothing on it says preview.
  • The sample data on our test server: when one admin pressed "Download the sample data", it was approved at once, and the open first-run page followed the load to the end without a reload. With two admins' first-run pages open on one address, both followed the load to the end, nobody was signed out and the server refused no request. An open page showed the other admin's request within 13 seconds of their press, without a reload. Each time the sample was added, Airflow showed one run of its load. From approval to loaded, the loads took between 5.5 and 7.6 minutes, and one took about 15 minutes. With the sample removed, the first pipeline's lesson pointed an admin to the button and told a member to ask an admin. sudo moorhold sample-data add with no --profile left the 26 services as they were, and sudo moorhold sample-data remove kept the password another source used, and said so.
  • On a test machine: a core server on 2026.10.16 updated to 2026.11.2, both by sudo moorhold upgrade and by the installer. Running the installer again says there's nothing to update. After a rollback, another update and a second rollback, the second update's rollback point left out the first rollback's kept copies, which stayed as they were, and the restore drill passed with them in place. The 2026.11.2 installer's check on an x86_64 server with nothing installed says the server is ready.
  • In the code and its tests: the ARM builds and how they are joined, the Node lines for both platforms, the installer's ARM refusal and its local mode, a local install and upgrade without an access key, the first-run page's checking, its pace, its waits and its limits, a stale press starting nothing, one admin's approval of the sample data and of more memory, one load run when the sample is added, the sample's password kept for another source, the proxy and download messages, the update window with backups off, a reader closing early, the rollback point without kept copies, the sample load's time on a server and on a Mac, sample-data add and the installed profile, the lesson's pointer to the button, the Mac app's first setup, its removal and its support details, and a preview build's update to a release.
  • Owed: the Updates page offering 2026.11.2 once it's Latest, the update window on a whole update, and this release's message behind a proxy that refuses get.moorhold.dev. Also owed: 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 on a server that holds a kept copy with a name of more than 47 bytes. An install on a real ARM machine is owed. Everything the Moorhold app for Mac does is owed on a Mac, from a first setup from its disk image to a real removal.

Images #

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

Still known #

  • A second admin for updates and Proposals. One admin is now enough for the sample data and for more memory only. On a server with two or more admins, an update asked for on the Updates page still waits for another admin to approve it, and a Proposal is still approved by someone other than the person who made it.
  • 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.
  • The audit page and one admin's request. The audit log stores "Asked for and approved by" and the admin's name for a sample data or memory request, but the portal's audit page doesn't show those words. On the page, an ask for the sample data is a setup.sample-ask row, and the server's work on it is two rows named requests.add-sample-data, one when it starts and one when it's done, with nothing on the page to tell them apart.
  • 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.
  • A request made near the end of the update. A sample data or memory request made in the portal near the end of the update to this release, once the portal is back, may not start until another request is approved. It stays approved, and an admin can cancel it.
  • Updating behind a proxy. The update to this release is checked by 2026.10.16's command. Behind a proxy that refuses get.moorhold.dev, it says only "fetch failed": ask for get.moorhold.dev to be allowed. If a proxy or firewall closes the connection part-way through a download, it can stop with an error from inside Node. Run it again, or update with the installer, which downloads with curl.
  • 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 and an update of the app and the stack over an install are owed on a Mac.
  • A Mac with 8 GB of memory. The Moorhold app for Mac needs 16 GB of memory. An 8 GB Mac hasn't been measured.
  • 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.
  • 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.
  • 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.

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.11.2.tar.gzcdde295918ff630e374e71e4e52c8d38cd2261ef9a97316ad4d8888ca96b805f
manifest.yamlcfa8590b8607e1c527516c721b1bd2a3ef96db7286ff2b8f1bb925343b75aada
release.lock498e27bea4ab68d571f1293ace9bb1a0afa0ae5893d634cb416ba1ae255f7ef3
install.sh7b009ce74481abe9f12bbcd45c288be19251e353e14bd74c18f8969c2ccc0123
cloud-init-ionos.yaml35a5c48901fc8301bf875c664c8a9a2291f6084af83a360cc976c4d3ff9ed433
cloud-init-hetzner.yaml9ee0f3352126278cf80170849ebde43141f71f5cc5128bafd25ca057102aa8a6
Moorhold-2026.11.2.dmg984bc2bf07740220e538384cbf541e959d493ecb7fdbb7d7f9c3bfa7150d2fc7
release.lock.minisigSignature, key 7F6D12F3F6217F9C
SHA256SUMSThe 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