Release state
Replaced #
This was the Latest release until 2026.10.13 replaced it. Before it became Latest, we updated our own Moorhold server to it from 2026.10.11, 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 fixes a security problem in the mail settings that 2026.10.11 brought in. Update to it from 2026.10.11 or from 2026.10.10. It's 2026.10.11 with this one fix, so if you're coming from 2026.10.10, 2026.10.11's notes say what else is new.
https://moorhold.dev/releases/2026.10.12Security fix
This release fixes a security problem #
- What's fixed
- 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.
- Manual steps
- None for most servers. If, after the update, the Mail page shows "Moorhold isn't using the saved mail settings.", enter the mail settings again with file:///run/secrets/smtp-password and save them. From 2026.10.10, also see 2026.10.11's notes: if you added a data source in the portal or with `moorhold apply -f`, run sudo moorhold apply once after the update, and if you changed the sample data's source file, see 2026.10.11's Updating.
Before you update #
- What changes
- 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.
- 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 anything, 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 most servers. If, after the update, the Mail page shows "Moorhold isn't using the saved mail settings.", enter the mail settings again with file:///run/secrets/smtp-password and save them. From 2026.10.10, also see 2026.10.11's notes: if you added a data source in the portal or with `moorhold apply -f`, run sudo moorhold apply once after the update, and if you changed the sample data's source file, see 2026.10.11's Updating.
- Still to be tested
- This release hasn't been through its test servers: the updates from 2026.10.10 and 2026.10.11, and the Mail page refusing any other password reference and clearing settings saved with one, are still to be tested.
Updating #
On a server running 2026.10.11 or 2026.10.10, update from the server's command line with:
sudo moorhold upgrade 2026.10.12
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.
Fixed #
- The mail server's password reference. On 2026.10.11 the Mail page took any secret reference as the mail server's password. So an admin could point it at another of the server's own secrets, and Keycloak could then send that secret to a mail server the admin chose. Only an admin who saved mail settings on 2026.10.11 could do this. The reference must now be file:///run/secrets/smtp-password, the password you set with
sudo moorhold mail password, or another file beside it namedsmtp-and then letters, digits or hyphens. For settings saved on 2026.10.11 with any other reference, Moorhold takes what it wrote out of Keycloak, and the Mail page shows "Moorhold isn't using the saved mail settings." Enter the settings again with file:///run/secrets/smtp-password and save them.
Verified #
- Owed: this release hasn't been through its test servers. This section says what was tested once it has.
Images #
Every one of Moorhold's own images is rebuilt from this release's source. No tool changes version, and the upstream images keep the digests they had in 2026.10.11.
Still known #
- Sending a test email from the Mail page. "Send a test email" opens a "We can't find that page" page and sends nothing. Saving and removing the mail settings work, and Keycloak uses settings saved with the right reference.
- Saving after leaving a page open. If you leave a portal page open for more than a few minutes and then save a change, you can see "Not a portal session: token expired." and nothing is saved. Reload the page, sign in again and save.
- 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.
- An update while a tool sleeps. The checks an update runs first count a sleeping tool's stopped services as failed, so the update refuses to start. Open each sleeping tool in your browser just before you update, and start the update straight away. An update approved for the maintenance window will keep refusing while a tool sleeps, so if you use sleeping, run your updates by hand.
- 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.
- 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.12.tar.gz | 220bef4217b0fe77c30a7b1494a3a3a19569f7a08d5943658a127a9868e13a02 |
| manifest.yaml | e22758bd450c93190577447a6b58e99a54075b5b1f505db6143af3cfc4c4156c |
| release.lock | 4bcfb237552eddbbe17bbcb25a7be3db0f07339a7bb1c29c44acf913541b22ae |
| install.sh | 8991352f2deac33868f020a7f7aaaf28799b8e242224b41fcd68b0c7ca78d6f8 |
| cloud-init-ionos.yaml | e861394fcd6c1ca43d2854ed0467f1f3c62fab195aee6f041c253aef9ccda3f2 |
| cloud-init-hetzner.yaml | e2d4cab0fd2a46336c58893aeaade004b76ccffcdcf84e028e254d5426d53648 |
| 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