-
Ekklesia v0.2.4 — External Module Installation & Persistence
Pre-ReleaseCI / verify (push) Successful in 1m13sCI / infrastructure-smoke (push) Successful in 38sCI / package-release (push) Successful in 49sCI / image-build (push) Successful in 30sCI / migration-smoke (push) Successful in 2m13sCI / deploy-smoke (same-origin) (push) Successful in 47sCI / package-publication (push) Successful in 1m4sCI / deploy-smoke (split) (push) Successful in 2m23sreleased this
2026-10-10 17:31:49 +00:00 | 0 commits to main since this releaseThis release completes the generic external-module installation path validated by the Signage integration.
Highlights- Supports installation and runtime use of real externally packaged Ekklesia modules.
- Persists installed module packages independently of the application container.
- Restores installed-module discovery and loading after process restart and container recreation.
- Preserves module lifecycle state, database data, and migration history across restarts and reinstall scenarios.
- Restores external-module integration coverage in CI.
- Validates module UI, runtime, migrations, lifecycle, and persistence against a real packaged module.
Integration validation
Ekklesia Signage was installed from its packaged artifact into generic Ekklesia and successfully validated through: - package verification and installation
- module migration application and idempotency
- discovery and runtime activation
- Dashboard UI loading
- module API operation
- display runtime and kiosk pairing in headless Chromium
- process restart
- API container recreation using persistent module and database volumes
- disable/re-enable
- remove/reinstall with preserved data and strict migration history
Core CI passed all 8 jobs for the final integration branch.
No production migrations are applied automatically; existing operator-controlled migration behavior remains unchanged.
Downloads
-
Ekklesia v0.2.3 — Native Verifier Hardening
Pre-ReleaseCI / verify (push) Successful in 1m8sCI / infrastructure-smoke (push) Successful in 28sCI / migration-smoke (push) Successful in 1m56sCI / package-release (push) Successful in 37sCI / image-build (push) Successful in 25sCI / deploy-smoke (same-origin) (push) Successful in 49sCI / deploy-smoke (split) (push) Successful in 1m22sCI / package-publication (push) Successful in 50sreleased this
2026-10-10 00:10:51 +00:00 | 7 commits to main since this releaseEkklesia v0.2.3 fixes native Module Package verification in hardened environments.
Highlights
- Adds a dedicated executable verifier scratch location for native runtime probes.
- Keeps general
/tmpstorage mountednoexec. - Preserves the hardened verifier boundary: non-root, read-only root filesystem, dropped capabilities, no unnecessary network access, and bounded ephemeral scratch.
- Fixes verification of native Node addons such as sharp/libvips without weakening package verification.
- Adds explicit verifier scratch configuration for supported hardened deployments.
Compatibility
There are no intentional breaking changes.
- Module Package format remains v1.
- Module manifest remains v8.
- Database ABI remains v1.
- Existing
^0.2.0platform and module SDK compatibility ranges remain valid.
Package train
All public
@ekklesia/*module-development packages are published as 0.2.3.Downloads
-
Ekklesia v0.2.2 — Corresponding Source & Native Redistribution
Pre-ReleaseCI / verify (push) Successful in 1m7sCI / infrastructure-smoke (push) Successful in 37sCI / migration-smoke (push) Successful in 1m54sCI / package-release (push) Successful in 35sCI / image-build (push) Successful in 12sCI / deploy-smoke (same-origin) (push) Successful in 49sCI / deploy-smoke (split) (push) Successful in 1m22sCI / package-publication (push) Successful in 1m0sreleased this
2026-10-09 22:17:11 +00:00 | 11 commits to main since this releaseEkklesia v0.2.2 adds the infrastructure required to publicly redistribute native Module Packages with covered third-party dependencies under Ekklesia's compliance policy.
Highlights
- Adds deterministic corresponding-source artifact generation.
- Adds the
ekklesia-corresponding-sourceCLI. - Adds fail-closed redistribution verification for native packages.
- Adds the libvips 1.3.4 corresponding-source recipe and rebuild metadata.
- Proves the sharp 0.35.5 / libvips 1.3.4 path end to end, including offline reconstruction from pinned source inputs.
- Marks ADR 0052 and ADR 0055 Accepted.
Compatibility
There are no intentional breaking changes.
- Module Package format remains v1.
- Module manifest remains v8.
- Database ABI remains v1.
- Existing
^0.2.0platform/module SDK compatibility ranges remain valid.
Package train
All public
@ekklesia/*module-development packages are published as 0.2.2.Downloads
-
Ekklesia v0.2.1 — Patched Native Module Support
Pre-ReleaseCI / verify (push) Successful in 1m8sCI / infrastructure-smoke (push) Successful in 37sCI / migration-smoke (push) Successful in 1m54sCI / package-release (push) Successful in 37sCI / image-build (push) Successful in 13sCI / deploy-smoke (same-origin) (push) Successful in 49sCI / deploy-smoke (split) (push) Successful in 1m21sCI / package-publication (push) Successful in 52sreleased this
2026-10-09 03:13:32 +00:00 | 16 commits to main since this releaseEkklesia v0.2.1 is a compatible patch release focused on native module packaging.
Highlights
- Adds reviewed license-supplement data for
@img/sharp-libvips-linux-x641.3.4. - Updates the native module proof from
sharp0.35.4 to the patchedsharp0.35.5 release. - Verifies
sharp0.35.5 packaging end to end onlinux-x64-glibc. - Preserves support for the existing libvips 1.3.3 supplement.
- Publishes the coordinated
@ekklesia/*0.2.1 package train.
Compatibility
There are no intentional breaking changes in this release.
- Module manifest version remains v8.
- Database ABI remains v1.
- Module Package format remains v1.
- Modules compatible with Ekklesia
^0.2.0remain compatible with 0.2.1.
Native packaging
The native proof now uses:
sharp0.35.5@img/sharp-linux-x640.35.5@img/sharp-libvips-linux-x641.3.4
The derived runtime requirements remain Node-API 9 and glibc 2.28 or newer.
Reviewed license supplements remain compliance inputs, not legal review or a determination that all redistribution obligations have been satisfied.
Downloads
- Adds reviewed license-supplement data for
-
Ekklesia v0.2.0 — Standalone Modules & Package Distribution
Pre-ReleaseCI / verify (push) Successful in 1m6sCI / infrastructure-smoke (push) Successful in 36sCI / migration-smoke (push) Successful in 1m56sCI / package-release (push) Successful in 34sCI / image-build (push) Successful in 11sCI / deploy-smoke (same-origin) (push) Successful in 49sCI / deploy-smoke (split) (push) Successful in 1m22sCI / package-publication (push) Successful in 47sreleased this
2026-10-09 00:28:24 +00:00 | 20 commits to main since this releaseEkklesia v0.2.0 is a breaking pre-1.0 release focused on making modules truly standalone, installable, and distributable outside the Ekklesia monorepo.
Highlights
- Introduces Ekklesia Module Package v1 for immutable, verifiable module packages.
- Adds manifest v8 and the new Module Database ABI v1.
- Modules can now build outside the Ekklesia monorepo using versioned
@ekklesia/*packages. - Publishes the first coordinated Ekklesia module-development package train.
- Adds reproducible package-release and standalone-consumer verification.
- Adds native module support for linux-x64-glibc, including native runtime dependencies.
- Adds reviewed third-party license supplement support for packaged native dependencies.
- Curates the public module SDK and removes legacy Drizzle database types from the public API.
- Moves installed modules outside the platform image so one generic Ekklesia image can run different module sets.
- Adds safe, resumable package publication with artifact round-trip verification.
Breaking changes
This release intentionally moves from the
0.1.xcompatibility line to0.2.x.Modules targeting Ekklesia 0.1.x are not automatically compatible with 0.2.0. In particular:
- manifest v7 is no longer accepted;
- modules should migrate to manifest v8;
- database-enabled modules should use Database ABI v1;
- legacy SDK exports such as
defineModuleSchemaand the oldModuleDatabasetype are no longer part of the public module SDK.
Ekklesia remains pre-1.0. Public APIs may continue to change between minor releases.
Downloads
-
v0.1.2
Pre-ReleaseCI / verify (push) Successful in 56sCI / infrastructure-smoke (push) Successful in 38sCI / migration-smoke (push) Successful in 1m51sCI / image-build (push) Successful in 7sCI / deploy-smoke (same-origin) (push) Successful in 41sCI / deploy-smoke (split) (push) Successful in 52sreleased this
2026-10-06 04:20:22 +00:00 What's Changed
- docs: the server runs Gitea 1.27.2, not 1.24.2; say what it actually honours in #61
- fix(ci): nothing a CI job starts outlives it, even when the runner kills the job in #60
- docs: propose ADR 0047, a published harness every module runs in CI in #59
- fix(deploy): reach storage over HTTP/1.1, and own storage CORS in the proxy in #58
- fix(deploy): give migrate the API's client-address settings, and say what Doctor checked in #57
- test(deploy): opt-in display-device scenarios for the split smoke in #56
Contributors
- @ekklesia-bot
Full Changelog: v0.1.1...v0.1.2
Downloads
-
v0.1.1: split origins, deployment, branding principle
Pre-ReleaseCI / verify (push) Successful in 1m27sCI / infrastructure-smoke (push) Successful in 22sCI / migration-smoke (push) Successful in 1m49sCI / image-build (push) Successful in 7sCI / deploy-smoke (same-origin) (push) Successful in 48sCI / deploy-smoke (split) (push) Successful in 45sreleased this
2026-10-03 20:02:55 +00:00 | 91 commits to main since this releaseFirst deployable release: container image, reference deployment, health endpoints, split Dashboard/API origins (ADR 0045), installation branding principle (ADR 0046).
Downloads
-
v0.1.0 — Phase 8 complete
Pre-Releasereleased this
2026-10-01 21:30:30 +00:00 | 115 commits to main since this releasePlatform foundation through Phase 8. First tagged version; not yet deployed.
Downloads