Release notes

This page lists every Marolum version published on Docker Hub and on this site, newest first, and what changed from one version to the next. Each version's notes list what it adds, changes and removes. They also list every database migration it applies, with its risk class, any deprecation it announces, and what changed in Known limitations. Read them before you upgrade, then follow Upgrades and versioning.

Versions

• Published as is how the version was first published. A tester is published for evaluation, and its tester.json says so. A version becomes a supported release only when its own supported.json is published beside it, with the same image and record; these notes do not change when that happens. 0.21.1 is the supported release.
• Released is the releasedAt date in the version's release.json. A version's documentation is preserved before its record is published, so its own copy of this page shows "In its release.json"; later copies show the date.
• Index digest is the multi-architecture image index for linux/amd64 and linux/arm64. Each version's records, frozen documentation and CLI are under https://www.dekglas.com/downloads/marolum/v<version>/.

Which version am I running?

Marolum shows its version in these places:

• Sign-in screen. The line under the sign-in form reads, for example, "Marolum Community · 0.21.1 · by Dekglas".

• About Marolum. Open your account menu and choose About Marolum. The Version row shows the version.

• Licensing. Administrators see "Version 0.21.1", for example, under Edition on the Licensing page.

• HTTP. GET /api/v1/readiness and GET /api/v1/health return a version field without signing in. Readiness answers only once the installation is ready.

  curl -s "$MAROLUM_URL/api/v1/readiness"
  # {"edition":"community","service":"marolum","status":"ready","version":"0.21.1"}
  

• CLI. marolum --version prints the CLI's version. The CLI archive for each version is marolum-cli-<version>.tgz in that version's downloads.

• Image label. The image carries the version in its org.opencontainers.image.version label. Read it from the running container, named marolum in these guides:

  docker inspect --format '{{ index .Config.Labels "org.opencontainers.image.version" }}' marolum
  

Match a running image to its release record

A version number names a release; the image digest proves which bytes are running.

1. Find the digest your installation runs. If you deployed by digest, that is the digest. Otherwise, with Docker, docker image inspect --format '{{json .RepoDigests}}' <image> lists docker.io/dekglas/marolum@sha256:…. On Kubernetes, kubectl get pod <pod> -o jsonpath='{.status.containerStatuses[*].imageID}' shows the digest the node pulled.
2. Open https://www.dekglas.com/downloads/marolum/v<version>/release.json for the version the installation reports. The digest should equal image.digest, the index in the table above. A runtime that reports a single platform's manifest instead should match that platform's entry in composition.image.platforms.
3. Check that the version's tester.json or supported.json names the same imageDigest, then verify the signature as Upgrades and versioning shows.

0.22.0-rc.1

Published as a tester for evaluation. Changes from 0.21.1. This candidate does not replace 0.21.1 as the supported release.

Source setup

Users with source-management permission can choose Add backend and add a filesystem source when the deployment operator has allowed exact read-only roots with MAROLUM_MANAGED_FILESYSTEM_ROOTS. The form selects an allowed root, tests access, and requires a new test after configuration changes. The browser cannot grant access to a new host path. Existing startup-file configuration remains available; PostgreSQL sources still use that configuration. Editing and removing saved sources are not added in this version. See Connect your backends for setup and engine-specific limits.

Test connection now checks an enabled saved source using bounded read access. Its result names the replica and completion time. A successful connection check does not establish fresh inventory or history and does not change the source configuration.

Runner setup

The matching CLI adds marolum check, a bounded connection and target-scope check for an integration token. It sends no operation evidence and starts no infrastructure command. A successful check does not establish that a stack exists, that capture is enabled, or that a later operation will be accepted. The Integration tokens page provides copyable checks and rotation guidance. See Runner integration.

Console

• Empty Overview pages offer first-run guidance appropriate to the signed-in role.
• An invalid route explains why the console returned to Overview.
• Resource-history permalinks wrap on narrow screens.
• Loading transitions stop after their component is removed, and affected controls have accessible names.
• Activation-key validation accepts the issuer's uppercase identifier and lowercase verifier spelling. It rejects altered spelling before submission; this does not activate a licence or change its grant.

Startup and PostgreSQL

A fresh PostgreSQL installation no longer needs an otherwise unused licensing directory. A refused start exits with an error instead of leaving an unready process running. Concurrent observation-read failures during startup are handled together, and integrity validation yields its database connection between bounded checks. These repairs do not change storage topology, database ownership or licence requirements.

Runtime and dependencies

The image remains on Node.js 26.10.0. Production dependency and base-image security updates are included; the exact versions, base digest, platform digests and attestations are in this version's composition record. A scan result describes that recorded build and is not a promise that no future vulnerability will be reported.

Database migrations

None. The schema remains 0101-runner-properties, as in 0.21.1 and 0.20.2. Take and verify the pre-upgrade backup as usual. An older image can start on this unchanged schema; restore the pre-upgrade backup for a rollback.

Deprecations and removals

None.

Known limitations

The PostgreSQL licensing-directory workaround through 0.21.1 is no longer needed in this version. Filesystem setup still requires operator-approved read-only mounts, and saved-source editing, removal and PostgreSQL credential setup remain outside the form. Other known limitations remain in force.

Screenshots

Existing guide figures retain their original version and synthetic-data captions. They are not relabeled as captures from this candidate.

0.21.1

Published as a tester. Changes from 0.21.0.

Help

The Editions and licensing section of the Help page no longer ends with "This development build does not enable public sales." It still sends you to the Marolum product page for current purchase availability and terms.

Runtime and dependencies

Unchanged from 0.21.0: the image is built on node:26.10.0-bookworm-slim, Node.js 26.10.0, with the same operating-system packages and the same production dependencies. The composition record in the version's release.json lists them.

Database migrations

None. A database that 0.21.0 has migrated is already at the schema 0.21.1 expects. Take the pre-upgrade backup as usual.

Deprecations

None.

Known limitations

Unchanged from 0.21.0.

Screenshots

The screenshots in these guides were captured on 0.20.2. None of them shows the Help page's Editions and licensing section, and none of the screens they show is different in 0.21.1.

0.21.0

Published as a tester. Changes from 0.20.2.

Account and pricing links

Four controls now open new addresses:

0.20.2 opened https://dekglas.com/account and https://dekglas.com/pricing. Both addresses now redirect to the new ones.

Runtime

The image is built on node:26.10.0-bookworm-slim, Node.js 26.10.0. 0.20.2 used Node.js 26.6.0. The image also includes Debian's PCRE2 and Perl security updates.

Dependencies

Three production dependencies moved:

The composition record in the version's release.json lists every production dependency.

Database migrations

None. A database that 0.20.2 has migrated is already at the schema 0.21.0 expects. Take the pre-upgrade backup as usual.

Deprecations

None.

Known limitations

Unchanged from 0.20.2.

Screenshots

The screenshots in these guides were captured on 0.20.2. None of the screens they show is different in 0.21.0.

0.20.2

Published as a tester on 2026-10-01. It is the first version published to docker.io/dekglas/marolum and to this site's downloads, so there is no earlier version to list changes from.

• One image, docker.io/dekglas/marolum:0.20.2, for Community, Business and Enterprise on linux/amd64 and linux/arm64.
• Built on node:26.6.0-bookworm-slim, Node.js 26.6.0, with SQLite 3.53.4 embedded.
• Its CLI is marolum-cli-0.20.2.tgz.
• Its record lists what it was verified against: Pulumi CLI 3.256.0, Pulumi deployment schema versions 0 to 4, SeaweedFS 4.47 as the S3-compatible store, and Chromium through Playwright 1.63.0.
• Its documentation is preserved at https://www.dekglas.com/downloads/marolum/v0.20.2/docs/.
• When it was published, Dekglas pointed the latest tag at it.