Zayin/Signage
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases 4 Wiki Activity

chore: release signage 0.1.3 #14

Merged
Zayin_Admin merged 1 commits from chore/release-0.1.3 into main 2026-10-10 17:34:55 +00:00
Conversation 1 Commits 1 Files Changed 8
+11 -11
ekklesia-bot commented 2026-10-10 17:21:28 +00:00
Member
Copy Link
Copy Source

chore: release signage 0.1.3

Proposal. After this merges, tag v0.1.3 on the merge commit. You create every tag; this PR creates none.

0.1.3 is the first release that ships as the external Module Package validated in #13 (Pass 2). This PR changes only the version. It follows the 0.1.2 release (#9, 855b5f9) and touches the same eight files.

What changes

File Change
ekklesia.module.json version 0.1.2 → 0.1.3
package.json version 0.1.2 → 0.1.3
src/server/runtime.ts runtime version and the settings payload's moduleVersion
src/ui/index.tsx, src/display/index.tsx module UI version
tests/manifest.test.ts, tests/browser/support/fake-host.ts expected version / fixture moduleVersion
README.md Status line: "Version 0.1.3 …"

Compatibility

  • compatibility.platform stays ^0.2.0 and moduleSdk stays ^0.2.0. Core 0.2.4 already satisfies both, so the range is not tightened.
  • @ekklesia/* dependencies, pnpm-workspace.yaml exemptions and ci/platform.env are unchanged. They are what #13 validated.
  • pnpm-lock.yaml has no root version field and is unchanged. pnpm install --frozen-lockfile passes.
  • No migration and no new dependency.

Validation (local)

  • pnpm install --frozen-lockfile: up to date
  • pnpm lint: passed
  • bash ci/check-cleanup.sh: passed
  • pnpm typecheck: passed
  • pnpm test: 22 files, 262 tests passed
  • pnpm build: passed
  • pnpm validate: [email protected] passed 20 checks (manifest, package.json and built runtime name one version)
  • ekklesia-pack-module --target linux-x64-glibc: Packed [email protected], signage-0.1.3-linux-x64-glibc.tar.gz, 133 files, checksum verified. In the extracted package, ekklesia.module.json, package.json and ekklesia.package.json all declare 0.1.3, the built runtime and both UI artifacts declare 0.1.3, and nothing declares 0.1.2.

I did not run the full external-package integration job locally. Gitea Actions runs it on this PR.

🤖 Generated with Claude Code

## chore: release signage 0.1.3 **Proposal.** After this merges, tag `v0.1.3` on the merge commit. You create every tag; this PR creates none. 0.1.3 is the first release that ships as the external Module Package validated in #13 (Pass 2). This PR changes only the version. It follows the 0.1.2 release (#9, `855b5f9`) and touches the same eight files. ### What changes | File | Change | |---|---| | `ekklesia.module.json` | `version` `0.1.2` → `0.1.3` | | `package.json` | `version` `0.1.2` → `0.1.3` | | `src/server/runtime.ts` | runtime `version` and the settings payload's `moduleVersion` | | `src/ui/index.tsx`, `src/display/index.tsx` | module UI `version` | | `tests/manifest.test.ts`, `tests/browser/support/fake-host.ts` | expected version / fixture `moduleVersion` | | `README.md` | Status line: "Version 0.1.3 …" | ### Compatibility - `compatibility.platform` stays **`^0.2.0`** and `moduleSdk` stays **`^0.2.0`**. Core 0.2.4 already satisfies both, so the range is not tightened. - `@ekklesia/*` dependencies, `pnpm-workspace.yaml` exemptions and `ci/platform.env` are unchanged. They are what #13 validated. - `pnpm-lock.yaml` has no root version field and is unchanged. `pnpm install --frozen-lockfile` passes. - No migration and no new dependency. ### Validation (local) - `pnpm install --frozen-lockfile`: up to date - `pnpm lint`: passed - `bash ci/check-cleanup.sh`: passed - `pnpm typecheck`: passed - `pnpm test`: 22 files, 262 tests passed - `pnpm build`: passed - `pnpm validate`: `[email protected] passed 20 checks` (manifest, package.json and built runtime name one version) - `ekklesia-pack-module --target linux-x64-glibc`: `Packed [email protected]`, `signage-0.1.3-linux-x64-glibc.tar.gz`, 133 files, checksum verified. In the extracted package, `ekklesia.module.json`, `package.json` and `ekklesia.package.json` all declare `0.1.3`, the built runtime and both UI artifacts declare `0.1.3`, and nothing declares `0.1.2`. I did not run the full external-package integration job locally. Gitea Actions runs it on this PR. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
ekklesia-bot added 1 commit 2026-10-10 17:21:28 +00:00
chore: release signage 0.1.3
CI / lint (pull_request) Successful in 11s
Details
CI / typecheck (pull_request) Successful in 11s
Details
CI / test (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 10s
Details
CI / integration (pull_request) Successful in 7m17s
Details
dd656eb18a 
0.1.3 ships the external package integration validated in #13 (Pass 2):
the canonical linux-x64-glibc Module Package installed and exercised
end to end by CI, with bounded external runtime image processing.

Only the version moves: the manifest, package.json, the server runtime,
both browser artifacts, the settings payload's moduleVersion, the test
fixtures, and the README status line. compatibility stays
platform ^0.2.0 and moduleSdk ^0.2.0; Core 0.2.4 already satisfies it,
so the range is not tightened. pnpm-lock.yaml carries no root version
and is unchanged.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Zayin_Admin merged commit 88a536464a into main 2026-10-10 17:34:55 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Zayin_Admin
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
Joey Zayin_Admin ekklesia-bot
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Zayin/Signage#14