Release notes / 2026.10.3

Early access release

Moorhold 2026.10.3 Replaced

Published

Release state

Replaced #

This was the Latest release until 2026.10.4 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 what our first full test install of 2026.10.2, done the way a customer would, ran into on 18 October 2026, on a clean Ubuntu 24.04 server behind a home connection.

https://moorhold.dev/releases/2026.10.3

Before you update #

What changes
Fixes an install failure on servers that can't reach their own public address, and the installer now always says what to do next.
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
A full install of this signed release, on a server that can't reach its own public address.

Fixed #

  • The install no longer fails when the server cannot reach its own public address.
    • The portal's agent server (portal MCP) and the portal itself now fetch the sign-in service's settings over the stack's own network, as the other tools have done since 2026.10.2.
    • Before this, a server whose router has no NAT loopback, or an install with --acme staging, failed at the end: the portal MCP server restarted for ever, and "Sign in with single sign-on" showed a blank error page.
    • The public address that tokens carry is unchanged.
  • The installer always says what to do next when the stack doesn't start. A failure on the second start, after the Stack is applied, used to end without a next step, a setup code or the address. It now prints the same guidance as a failure on the first start.

Verified #

  • Unit and golden tests: 2,161 tests pass.
  • On the rehearsal server, with the fix applied by hand before this release:
    • the portal MCP server started;
    • the first-run wizard set the admin password and ran the sample pipeline;
    • the admin account signed in to Superset, DataHub and Airflow.
  • Owed: a full install of this signed release, on a server that can't reach its own public address.

Images #

The shell, reconciler, collector and portal MCP images are rebuilt. Every other image keeps the digest it had in 2026.10.2.

Still known #

  • Using Moorhold from inside the same network. If your router has no NAT loopback, a browser on the same network as the server cannot open your Moorhold address yet. Use it from outside, or add a hosts-file entry as the guide says. A fix is being built: the installer will detect this and offer an optional relay, a small server of your own. Added in 2026.10.4.
  • Signing in to the tools. Opening a tool after the setup wizard still shows that tool's own sign-in page, then the sign-in service's page. Setup will sign you in once for every tool in a later release.
  • The sample data has no dashboard yet. Superset opens with the sample datasets but no chart.
  • 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.3.tar.gz59db6ae185db83727edeb855e046d4f27936a66c73c737a2155edbae22548b85
release.locke0364fd04e015df3c6e318a37fae22fd70fbe9acdb71479eb35812a58a29f408
install.sh322c56e45ab69871c35a78a62fbd63726dd4850d91d0f8edc1fbe9827473fa1c
cloud-init-ionos.yamlc1100d9480a91215bc72a4ec308319cceabb440fb385b9a56937048be2d1bbb4
cloud-init-hetzner.yamle4d0a349a06f376cbfe7b799247c190f76bbb5b4111c264d4cdf3f443e1d5354
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