Author SHA1 Message Date
Zayin_Admin dd06d63007 Merge pull request 'chore: release signage 0.1.5' (#22) from release/0.1.5 into main
CI / typecheck (push) Successful in 24s
CI / lint (push) Successful in 25s
CI / build (push) Successful in 26s
CI / test (push) Successful in 28s
CI / package (push) Successful in 24s
CI / integration (push) Successful in 8m36s
Reviewed-on: #22
Reviewed-by: Zayin_Admin <[email protected]>
2026-10-14 05:43:32 +00:00
ekklesiaandClaude Opus 5.5 49fdd446ef chore: release signage 0.1.5
CI / typecheck (pull_request) Successful in 25s
CI / lint (pull_request) Successful in 26s
CI / build (pull_request) Successful in 25s
CI / test (pull_request) Successful in 28s
CI / package (pull_request) Successful in 23s
CI / integration (pull_request) Successful in 8m48s
Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-14 00:20:59 -05:00
Zayin_Admin c04506ba7b Merge pull request 'ci: pin the platform harness to the released Core v0.2.5' (#21) from ci/pin-platform-v0.2.5 into main
CI / lint (push) Successful in 26s
CI / typecheck (push) Successful in 26s
CI / build (push) Successful in 26s
CI / test (push) Successful in 28s
CI / package (push) Successful in 23s
CI / integration (push) Successful in 8m49s
Reviewed-on: #21
Reviewed-by: Zayin_Admin <[email protected]>
2026-10-14 05:18:23 +00:00
ekklesiaandClaude Opus 5.5 c1213dad08 ci: pin the platform harness to the released Core v0.2.5
CI / lint (pull_request) Successful in 19s
CI / typecheck (pull_request) Successful in 18s
CI / test (pull_request) Successful in 23s
CI / build (pull_request) Successful in 19s
CI / package (pull_request) Successful in 22s
CI / integration (pull_request) Successful in 8m47s
Integration still fetched Core at PR #92's head (5e9433d): the right
pin while that PR was in review, but it predates #94 (display
credential renewal) and #93 (the registry move), both in v0.2.5. Signage
now proves itself against the release it will run on.

The pin contract also accepts a release tag (refs/tags/vX.Y.Z) alongside
a pull request head or main, and the fetch compares the ref's commit
(^{commit}) so an annotated tag pins the same way a lightweight one
does. v0.2.5 is lightweight; that should not be a hidden requirement.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-14 00:05:15 -05:00
Zayin_Admin ba4821ec63 Merge pull request 'docs(claude): file an issue for what you find outside the task' (#20) from docs/claude-md-report-findings into main
CI / lint (push) Successful in 17s
CI / typecheck (push) Successful in 19s
CI / test (push) Successful in 26s
CI / build (push) Successful in 19s
CI / package (push) Successful in 22s
CI / integration (push) Successful in 9m11s
Reviewed-on: #20
Reviewed-by: Zayin_Admin <[email protected]>
2026-10-14 04:18:43 +00:00
12 changed files with 20 additions and 19 deletions
+1 -1
View File
@@ -3,7 +3,7 @@ name: CI
# Signage is a standalone repository: every job installs it with --frozen-lockfile from its own
# pnpm-lock.yaml and takes Ekklesia's module-development packages (@ekklesia/*) from Ekklesia's
# public package registry (.npmrc; platform ADRs 0053 and 0054). Only the integration job fetches
# Core source: one immutable commit through the pinned Gitea pull ref in ci/platform.env, used as the
# Core source: one immutable commit through the pinned Gitea ref in ci/platform.env, used as the
# generic deployment harness and image source, never as a workspace dependency.
#
# The same trust rules as the platform's own CI (docs/development/security.md there):
+1 -1
View File
@@ -16,7 +16,7 @@ Ekklesia and vendors none of its SDKs.
## Status
Version 0.1.4 is feature-complete for its declared scope, and Signage has run in production since
Version 0.1.5 is feature-complete for its declared scope, and Signage has run in production since
0.1.1. What exists today:
- The module package, manifest (v8), four capabilities, six permissions, ten operator settings, and
+2 -2
View File
@@ -40,9 +40,9 @@ check '[[ -n "$own" && -n "$run" ]] && ((own > run)) && ((own > last_step))' \
check 'sed -n "${last_step},\$p" <<<"$job" | grep -q "if: always()"' "that last step always runs"
check 'grep -q "EKKLESIA_SMOKE_MODULE_RELEASE_DIR" "$root/ci/integration.sh" && grep -q "bash scripts/smoke-deploy.sh" "$root/ci/integration.sh"' \
"the integration delegates its external package to the platform smoke"
check 'grep -Eq "^EKKLESIA_PLATFORM_REF=refs/(pull/[0-9]+/head|heads/main)$" "$root/ci/platform.env" && grep -Eq "^EKKLESIA_PLATFORM_COMMIT=[0-9a-f]{40}$" "$root/ci/platform.env"' \
check 'grep -Eq "^EKKLESIA_PLATFORM_REF=refs/(pull/[0-9]+/head|heads/main|tags/v[0-9]+\.[0-9]+\.[0-9]+)$" "$root/ci/platform.env" && grep -Eq "^EKKLESIA_PLATFORM_COMMIT=[0-9a-f]{40}$" "$root/ci/platform.env"' \
"the platform harness is pinned by full ref and commit"
check 'grep -q "rev-parse refs/remotes/pinned" "$root/ci/fetch-platform.sh" && grep -q "does not resolve to EKKLESIA_PLATFORM_COMMIT" "$root/ci/fetch-platform.sh"' \
check 'grep -qF "rev-parse \"refs/remotes/pinned^{commit}\"" "$root/ci/fetch-platform.sh" && grep -q "does not resolve to EKKLESIA_PLATFORM_COMMIT" "$root/ci/fetch-platform.sh"' \
"the fetch verifies that the pinned ref resolves to the pinned commit"
# Normal CI builds the canonical archive once and hands those exact bytes to integration through a
+1 -1
View File
@@ -32,7 +32,7 @@ git -C "$out" init --quiet
git -C "$out" remote add origin "$repository"
git -C "$out" fetch --quiet --no-tags --depth=1 origin "+${ref}:refs/remotes/pinned" ||
fail "cannot fetch the pinned platform ref."
[[ "$(git -C "$out" rev-parse refs/remotes/pinned)" == "$commit" ]] ||
[[ "$(git -C "$out" rev-parse "refs/remotes/pinned^{commit}")" == "$commit" ]] ||
fail "the pinned ref does not resolve to EKKLESIA_PLATFORM_COMMIT."
git -C "$out" -c advice.detachedHead=false checkout --quiet --detach "$commit"
rm -rf "$out/.git"
+5 -4
View File
@@ -1,5 +1,6 @@
# The companion Core harness Signage uses to install and run its real external package. The pull ref
# remains reachable after its branch is deleted; the full commit pin makes the checkout immutable.
# The companion Core harness Signage uses to install and run its real external package: a released
# Core, by its tag. A pull request's ref (refs/pull/N/head) is used only while Signage depends on a
# Core change still in review. The full commit pin makes the checkout immutable either way.
EKKLESIA_PLATFORM_REPOSITORY=https://git.zayin.net/Zayin/Ekklesia.git
EKKLESIA_PLATFORM_REF=refs/pull/92/head
EKKLESIA_PLATFORM_COMMIT=5e9433d96b413117374a6132d89400867414c2c8
EKKLESIA_PLATFORM_REF=refs/tags/v0.2.5
EKKLESIA_PLATFORM_COMMIT=437720f2286e962829f2ec8c1c6137ea24f87b9f
+1 -1
View File
@@ -3,7 +3,7 @@
"id": "signage",
"name": "Signage",
"description": "Visual programming, timelines, synchronized channels, and display delivery for church screens.",
"version": "0.1.4",
"version": "0.1.5",
"compatibility": {
"platform": "^0.2.0",
"moduleSdk": "^0.2.0"
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "@ekklesia/signage",
"version": "0.1.4",
"version": "0.1.5",
"private": true,
"license": "AGPL-3.0-or-later",
"type": "module",
+1 -1
View File
@@ -59,7 +59,7 @@ function SignageDisplay({ context }: { readonly context: ModuleUiHostContext }):
*/
export default defineModuleUi({
id: "signage",
version: "0.1.4",
version: "0.1.5",
styles: displayStyles,
mount(container, context) {
const root = createRoot(container);
+2 -2
View File
@@ -130,7 +130,7 @@ export function createSignageModuleRuntime(
// Database ABI v1 executor, which `createSignageStore` binds Signage's own Drizzle adapter to.
database: { abi: 1 },
id: "signage",
version: "0.1.4",
version: "0.1.5",
register({ capabilities, config, http, realtime }) {
const settings = readSignageSettings(config);
@@ -192,7 +192,7 @@ export function createSignageModuleRuntime(
// server enforces — a UI believing a stale limit would offer an upload the server refuses.
return Response.json({
crossfadeMs: current.crossfadeMs,
moduleVersion: "0.1.4",
moduleVersion: "0.1.5",
nativeImageDurationMs: current.nativeImageDurationMs,
nativePresentation: current.nativePresentation,
rendererInputVersion: SIGNAGE_SLIDE_RENDERER_INPUT_VERSION,
+1 -1
View File
@@ -15,7 +15,7 @@ import ownStyles from "./styles.css";
*/
export default defineModuleUi({
id: "signage",
version: "0.1.4",
version: "0.1.5",
styles: `${EKKLESIA_UI_STYLESHEET}\n${ownStyles}`,
mount(container, context) {
const root = createRoot(container);
+1 -1
View File
@@ -117,7 +117,7 @@ export function createFakeHost(options: FakeHostOptions): FakeHost {
/** The settings payload every screen loads first. */
export const FAKE_SETTINGS = Object.freeze({
crossfadeMs: 1000,
moduleVersion: "0.1.4",
moduleVersion: "0.1.5",
nativeImageDurationMs: 7000,
nativePresentation: {
backgroundColor: "#000000",
+3 -3
View File
@@ -66,7 +66,7 @@ describe("Signage module manifest", () => {
expect(manifest.manifestVersion).toBe(8);
expect(manifest.id).toBe("signage");
expect(manifest.name).toBe("Signage");
expect(manifest.version).toBe("0.1.4");
expect(manifest.version).toBe("0.1.5");
expect(manifest.compatibility).toEqual({ moduleSdk: "^0.2.0", platform: "^0.2.0" });
});
@@ -151,7 +151,7 @@ describe("Signage module manifest", () => {
describe("Signage server runtime", () => {
it("exports the typed runtime definition the compiled server entrypoint publishes", async () => {
// The runtime's database declaration must match the manifest's, or Core refuses to start it.
expect(moduleRuntime).toMatchObject({ database: { abi: 1 }, id: "signage", version: "0.1.4" });
expect(moduleRuntime).toMatchObject({ database: { abi: 1 }, id: "signage", version: "0.1.5" });
});
it("registers its routes declaratively, with no database, storage, or realtime work", async () => {
@@ -251,7 +251,7 @@ describe("Signage server runtime", () => {
expect(response.status).toBe(200);
expect(await response.json()).toEqual({
crossfadeMs: 400,
moduleVersion: "0.1.4",
moduleVersion: "0.1.5",
nativeImageDurationMs: 12_000,
nativePresentation: SIGNAGE_DEFAULT_SETTINGS.nativePresentation,
rendererInputVersion: "1.0.0",