chore(release): prepare 0.1.2 #62

2026-10-06T03:56:48Z

ekklesia-bot commented

2026-10-06 03:56:48 +00:00

chore(release): prepare 0.1.2

⚠ The existing tag v0.1.2 cannot be used as is.

It points at 12dca3e (#61's merge), where every package.json still says 0.1.1.
The instance's scripts/assemble.sh checks exactly this, and refuses: "the platform at v0.1.2 reports version 0.1.1; its tag and package.json disagree."
The running platform would also report itself as 0.1.1.
For 0.1.1, a release PR bumped the versions before tagging (chore(release): prepare 0.1.1 …). This is the same step for 0.1.2.

Retagging: your call

Recommended, if nothing has consumed v0.1.2 yet (the instance hasn't pinned it): delete the tag, merge this PR, and create v0.1.2 again on this PR's merge commit.
Otherwise: leave v0.1.2 as an unused tag, change this PR to 0.1.3, and tag that.

Changes

The 12 workspace package.json files: 0.1.1 → 0.1.2. Same set as the 0.1.1 release; templates/module keeps its own version.
deploy/README.md: the build example's VERSION and image tag.

No other literal 0.1.1 exists in the repository.

What 0.1.2 carries

#57: Doctor checks the client-address configuration the API runs.
#58: storage over HTTP/1.1, so repeat image loads no longer fail with ERR_HTTP2_PROTOCOL_ERROR; storage CORS owned by the proxy. Production needs this.
#60: CI stacks never outlive their job.
#56: display-device smoke scenarios.
#59, #61: ADR 0047 proposed; CI docs corrected for Gitea 1.27.2.

Verification

pnpm verify passes.

The first verify run failed with two core import-safety tests (doctor-import, module-http-import) at Vitest's default 5 s timeout, while every package's tests ran in parallel. Alone they pass, twice, and a full rerun passes. Timing flakiness under load: I'll address it in the CI-speed work rather than here.

🤖 Generated with Claude Code

## chore(release): prepare 0.1.2 **⚠ The existing tag `v0.1.2` cannot be used as is.** - It points at `12dca3e` (#61's merge), where every `package.json` still says **`0.1.1`**. - The instance's `scripts/assemble.sh` checks exactly this, and refuses: *"the platform at v0.1.2 reports version 0.1.1; its tag and package.json disagree."* - The running platform would also report itself as 0.1.1. - For 0.1.1, a release PR bumped the versions before tagging (`chore(release): prepare 0.1.1 …`). This is the same step for 0.1.2. ### Retagging: your call 1. **Recommended, if nothing has consumed `v0.1.2` yet** (the instance hasn't pinned it): delete the tag, merge this PR, and create `v0.1.2` again on this PR's merge commit. 2. **Otherwise:** leave `v0.1.2` as an unused tag, change this PR to 0.1.3, and tag that. ### Changes - The 12 workspace `package.json` files: `0.1.1` → `0.1.2`. Same set as the 0.1.1 release; `templates/module` keeps its own version. - `deploy/README.md`: the build example's `VERSION` and image tag. No other literal `0.1.1` exists in the repository. ### What 0.1.2 carries - #57: Doctor checks the client-address configuration the API runs. - #58: storage over HTTP/1.1, so repeat image loads no longer fail with `ERR_HTTP2_PROTOCOL_ERROR`; storage CORS owned by the proxy. **Production needs this.** - #60: CI stacks never outlive their job. - #56: display-device smoke scenarios. - #59, #61: ADR 0047 proposed; CI docs corrected for Gitea 1.27.2. ### Verification `pnpm verify` passes. The first `verify` run failed with two core import-safety tests (`doctor-import`, `module-http-import`) at Vitest's default 5 s timeout, while every package's tests ran in parallel. Alone they pass, twice, and a full rerun passes. Timing flakiness under load: I'll address it in the CI-speed work rather than here. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ekklesia-bot added 1 commit 2026-10-06 03:56:48 +00:00

chore(release): prepare 0.1.2

CI / verify (pull_request) Successful in 55s

Details

CI / infrastructure-smoke (pull_request) Successful in 36s

Details

CI / migration-smoke (pull_request) Successful in 1m51s

Details

CI / image-build (pull_request) Successful in 27s

Details

CI / deploy-smoke (same-origin) (pull_request) Successful in 42s

Details

CI / deploy-smoke (split) (pull_request) Successful in 1m11s

Details

5abc8be167

Every workspace package declares 0.1.2, as the 0.1.1 release did for
itself, and the deploy README's build example names it. The tag
v0.1.2 created on 12dca3e carries package.json 0.1.1, which the
instance's assemble.sh refuses ("its tag and package.json disagree"),
and the running platform would report 0.1.1.

0.1.2 carries what the first production deployment found:
- #57: Doctor checks the client-address configuration the API runs;
- #58: storage over HTTP/1.1 (repeat image loads no longer fail with
  ERR_HTTP2_PROTOCOL_ERROR), and storage CORS owned by the proxy;
- #60: CI stacks never outlive their job;
- #56: display-device smoke scenarios;
- #59, #61: ADR 0047 proposed, and the CI documentation corrected for
  Gitea 1.27.2.

templates/module keeps its own version.

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

Zayin_Admin approved these changes

2026-10-06 04:08:53 +00:00

Zayin_Admin merged commit fc504eee0a into main

2026-10-06 04:08:58 +00:00

Zayin_Admin deleted branch chore/release-0.1.2

2026-10-06 04:08:58 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Zayin/Ekklesia#62