Release notes / 2026.10.2

Early access release

Moorhold 2026.10.2 Replaced

Published

Release state

Replaced #

This was the Latest release until 2026.10.3 replaced it. That was before we ran each Latest release on our own Moorhold server first. There's no in-place update from this release. Email hello@moorhold.dev and we'll help you move to 2026.11.4.

This release fixes the problems our own home-lab install of 2026.10.1 ran into on 11 October 2026. Every fix passes our unit and golden tests, but nobody has yet re-run a full install with them, so please treat this as a test release and tell us what breaks.

https://moorhold.dev/releases/2026.10.2

Before you update #

What changes
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.
Downtime
Not known yet: there's no one-step upgrade. See Upgrading.
Backup
Updating doesn't take a backup for you yet.
Manual steps
Yes: there's no one-step upgrade yet. See Upgrading.
Still to be tested
Nobody has yet re-run a full install with these fixes, so please treat this as a test release and tell us what breaks.

Fixed #

  • File permissions under a strict umask. The installer runs with umask 077, which could leave the project, the Stack, the release and the DAGs directories unreadable to containers that do not run as root. They now get explicit modes. Secrets stay 0600 in 0700 directories.
  • Sign-in between services inside the stack. DataHub, Superset, Airflow, Trino, Polaris and SeaweedFS now reach Keycloak over the project's own network for OIDC discovery and keys, instead of going out through the public hostname. The public issuer is unchanged.
  • The installer stops when the stack doesn't start. If docker compose up fails for any reason other than the portal waiting for its Stack, the installer stops and says what to do next, instead of carrying on.
  • Trino restarts cleanly. Trino removes a stale launcher pid file every time it starts.
  • You can sign in after the setup wizard. Step 1 of the first-run wizard now also creates your first Keycloak user, in shipboard-admins, with the password you set. If Keycloak refuses, nothing is saved and you can submit the form again. An existing user is never reset or promoted. Stacks that sign in through an organisation's own identity provider are left alone. This is tested against a fake Keycloak admin API only, not a real Keycloak yet.

Images #

The shell, reconciler, collector and portal MCP images are rebuilt, and all four pass our licence checks. Every other image keeps the digest it had in 2026.10.1.

Still known #

  • Installing on a home network without public DNS or NAT loopback still needs a hosts-file entry on the machine you browse from.
  • 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.

Each newer 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.10.2.tar.gz9da26ca6ba48a06b0be9d4b315c4f8bbe9f4d35e6c76d30b7c07319f6e092155
release.lock0a5d90600a8e58583e9930875cb62a9cda9468d36af48763355bee820cccaab5
install.sh2ea213863539a3c7b5eaf6f968479fec2289dc28f4f765443250eb18cfc4cca3
cloud-init-ionos.yaml3457464a983993cc73ec8f7bea645a0eeef3a4d6160222796a9e1832e7fab1e6
cloud-init-hetzner.yaml289504a7459e5139bef15757dba3f9e2a4d42f143ae5977f8846930f3982accf
release.lock.minisigSignature, key 7F6D12F3F6217F9C
SHA256SUMSThe checksums above
minisign -Vm release.lock -p moorhold-release.pub
sha256sum -c SHA256SUMS

Public key: get.moorhold.dev/moorhold-release.pub