chore: release signage 0.1.5 #22

Merged

Zayin_Admin merged 1 commits from release/0.1.5 into main 2026-10-14 05:43:32 +00:00

Conversation 0 Commits 1 Files Changed 8

+11 -11

ekklesia-bot commented 2026-10-14 05:33:14 +00:00

Member

Copy Link

Copy Source

Prepares Signage 0.1.5 from current main (c04506b): the Stage 0 production-readiness fixes (#18), the issue-reporting rule (#20), and the CI harness pinned to the released Core v0.2.5 (#21).

Version changes

Signage 0.1.4 → 0.1.5 in the same 8 files and 11 places as the 0.1.4 release (#17): package.json, ekklesia.module.json, src/server/runtime.ts (runtime version and the settings response's moduleVersion), src/display/index.tsx, src/ui/index.tsx, the README status line, tests/manifest.test.ts, and tests/browser/support/fake-host.ts. No other 0.1.4 remains.

Platform and dependencies, deliberately unchanged

• CI/release harness: already pinned to Core refs/tags/v0.2.5 @ 437720f (#21).
• Compatibility range: platform ^0.2.0, moduleSdk ^0.2.0. Nothing in the contract requires a change.
• @ekklesia/* build dependencies: stay at 0.2.3 (lockfile unchanged). The only package source change from 0.2.3 to 0.2.5 is a new helper, isModuleStorageError, for the cross-package instanceof ModuleStorageError problem. Signage already identifies storage errors by shape (src/server/images/service.ts:24-31), so it has no use for it. The integration below proves a package built with module-pack 0.2.3 installs and runs on Core 0.2.5.

Checks (local, at 49fdd44)

Check	Result
pnpm install --frozen-lockfile	pass
pnpm lint, pnpm typecheck	pass
pnpm test	pass, 289 tests
pnpm build	pass
pnpm validate	pass, [email protected], 20 checks
bash ci/check-cleanup.sh	pass
python3 -m unittest ci/test_release_assets.py	pass, 5 tests
bash ci/package.sh build/release-assets	signage-0.1.5-linux-x64-glibc.tar.gz, 133 files, sha256 fc5c45e3c07e07a282f7851bf952e38d6c3fffde886c61f255bb3c3e66f966ec
python3 ci/release-assets.py verify-package build/release-assets v0.1.5 49fdd44…	pass
bash ci/fetch-platform.sh + bash ci/integration.sh build/release-assets against Core v0.2.5	pass: 163 ok, 0 failed. Package verified by the platform; all seven display scenarios (two-pages, session-blip, stream-failure, stream-recycle, connectivity-blip, caching-probe, revoke); API process restart and container recreation; disable/re-enable; remove/reinstall; doctor READY

The package hash above is from a local build. The release workflow builds and verifies its own.

No tag is created. The release (v0.1.5) is made manually after merge.

🤖 Generated with Claude Code

Prepares Signage **0.1.5** from current `main` (`c04506b`): the Stage 0 production-readiness fixes (#18), the issue-reporting rule (#20), and the CI harness pinned to the released Core v0.2.5 (#21). ## Version changes Signage `0.1.4` → `0.1.5` in the same 8 files and 11 places as the 0.1.4 release (#17): `package.json`, `ekklesia.module.json`, `src/server/runtime.ts` (runtime version and the settings response's `moduleVersion`), `src/display/index.tsx`, `src/ui/index.tsx`, the README status line, `tests/manifest.test.ts`, and `tests/browser/support/fake-host.ts`. No other `0.1.4` remains. ## Platform and dependencies, deliberately unchanged - **CI/release harness:** already pinned to Core **`refs/tags/v0.2.5` @ `437720f`** (#21). - **Compatibility range:** `platform ^0.2.0`, `moduleSdk ^0.2.0`. Nothing in the contract requires a change. - **`@ekklesia/*` build dependencies:** stay at `0.2.3` (lockfile unchanged). The only package source change from 0.2.3 to 0.2.5 is a new helper, `isModuleStorageError`, for the cross-package `instanceof ModuleStorageError` problem. Signage already identifies storage errors by shape (`src/server/images/service.ts:24-31`), so it has no use for it. The integration below proves a package built with `module-pack` 0.2.3 installs and runs on Core 0.2.5. ## Checks (local, at `49fdd44`) | Check | Result | |---|---| | `pnpm install --frozen-lockfile` | pass | | `pnpm lint`, `pnpm typecheck` | pass | | `pnpm test` | pass, 289 tests | | `pnpm build` | pass | | `pnpm validate` | pass, `[email protected]`, 20 checks | | `bash ci/check-cleanup.sh` | pass | | `python3 -m unittest ci/test_release_assets.py` | pass, 5 tests | | `bash ci/package.sh build/release-assets` | `signage-0.1.5-linux-x64-glibc.tar.gz`, 133 files, sha256 `fc5c45e3c07e07a282f7851bf952e38d6c3fffde886c61f255bb3c3e66f966ec` | | `python3 ci/release-assets.py verify-package build/release-assets v0.1.5 49fdd44…` | pass | | `bash ci/fetch-platform.sh` + `bash ci/integration.sh build/release-assets` against **Core v0.2.5** | pass: 163 ok, 0 failed. Package verified by the platform; all seven display scenarios (two-pages, session-blip, stream-failure, stream-recycle, connectivity-blip, caching-probe, revoke); API process restart and container recreation; disable/re-enable; remove/reinstall; doctor READY | The package hash above is from a local build. The release workflow builds and verifies its own. No tag is created. The release (`v0.1.5`) is made manually after merge. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ekklesia-bot added 1 commit 2026-10-14 05:33:14 +00:00

chore: release signage 0.1.5 ... 49fdd446ef

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Zayin_Admin approved these changes 2026-10-14 05:35:21 +00:00

Zayin_Admin merged commit dd06d63007 into main 2026-10-14 05:43:32 +00:00

Zayin_Admin deleted branch release/0.1.5 2026-10-14 05:43:32 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Zayin_Admin

Labels

Clear labels

found-by-claude

Found by Claude while working on another task

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

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Zayin/Signage#22