fix(celilo): declare public_web 4.0.0 and bundle capabilities ^5.1.1 #76

Open

forgejo-admin wants to merge 1 commit from fix/public-web-4-declaration into main

forgejo-admin commented

2026-09-27 07:34:15 +00:00

Owner

Problem

This commit (e8a3f61, 2026-09-24) was pushed to fix/public-web-4-declaration but never opened as a PR, so main still has:

manifest.yml requiring public_web 3.0.0, while deployed caddy provides 4.0.0. celilo refuses that as major_mismatch_lower; the registry poll defers and retries forever, so the module reads healthy while upgrades never land (celilo#1414).
celilo/scripts bundling @celilo/capabilities ^3.4.0. The caret can't cross a major, so hooks run the 3.x implementation while the source calls the 4.x API (celilo#173).

The hook code already moved to public_web 4.0.0 in 1.6.0; only the declaration lagged.

Solution

Bump both together: public_web → 4.0.0 in manifest.yml, @celilo/capabilities → ^5.1.1 in celilo/scripts.

Found while auditing main after closing #73. The branch is based on 9862e61 and merges cleanly into current main; CI has not yet run on it.

🤖 Generated with Claude Code

## Problem This commit (`e8a3f61`, 2026-09-24) was pushed to `fix/public-web-4-declaration` but never opened as a PR, so `main` still has: - `manifest.yml` requiring `public_web` **3.0.0**, while deployed caddy provides 4.0.0. celilo refuses that as `major_mismatch_lower`; the registry poll defers and retries forever, so the module reads healthy while upgrades never land (celilo#1414). - `celilo/scripts` bundling `@celilo/capabilities` **^3.4.0**. The caret can't cross a major, so hooks run the 3.x implementation while the source calls the 4.x API (celilo#173). The hook code already moved to public_web 4.0.0 in 1.6.0; only the declaration lagged. ## Solution Bump both together: `public_web` → 4.0.0 in `manifest.yml`, `@celilo/capabilities` → ^5.1.1 in `celilo/scripts`. Found while auditing `main` after closing #73. The branch is based on `9862e61` and merges cleanly into current `main`; CI has not yet run on it. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

forgejo-admin added 1 commit

2026-09-27 07:34:15 +00:00

fix(celilo): declare public_web 4.0.0 and bundle capabilities ^5.1.1

pr-validate / validate (pull_request) Failing after 24s

Details

e8a3f61124

lunacycle's hook code migrated to the public_web 4.0.0 contract in 1.6.0
(publish-static-site-web-root): the SPA moved to site/dist via vite's
outDir, publishStaticSite's sourceDir argument was dropped, and client
config moved broker-side to window.__MODULE_CONFIG__ because writing
config.js into the module's own tree died EROFS under celilo's hook jail
(lu-ciy). The declaration never followed the code.

Two halves, and either alone leaves it broken:

requires.capabilities still said public_web 3.0.0 while deployed caddy
provides 4.0.0. That is major_mismatch_lower, which celilo refuses at
validation — and the registry poll then defers it and retries forever
rather than reporting a failure, so the module reads healthy while its
upgrades can never land (celilo#1414).

celilo/scripts bundled @celilo/capabilities ^3.4.0. A caret cannot cross
a major, so the hook ran the 3.x implementation while its source called
the 4.x API. Modules run their bundled copy (celilo#173), so the version
a module declares and the one it executes have to be moved together.

Verified: bun install pulled 5.1.1; `bun run test:hooks` (CI's own
invocation, --frozen-lockfile) 67 pass 0 fail; `celilo module check .`
9 ok, 3 warn, 0 fail.

Not verified, and worth knowing: the module has no scripts/tsconfig.json,
so nothing typechecks these hooks against current @celilo types — the
5.1.1 pin is proven by unit tests only. `module check` warns about it.

The fleet is still on 1.4.2+1 in ERROR; 1.6.0 was merged but never
published because the registry upload timed out (lu-970), so this rides
on top of that rather than replacing it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

forgejo-admin referenced this pull request from celilo/celilo

2026-10-04 00:21:22 +00:00

Explain why lunacycle is in ERROR on celilo-mgr: caddy cannot serve it, "no built site at /var/celilo/modules/lunacycle/site/dist" #1557

pr-validate / validate (pull_request) Failing after 24s

Details

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin fix/public-web-4-declaration:fix/public-web-4-declaration

git switch fix/public-web-4-declaration

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff fix/public-web-4-declaration

git switch fix/public-web-4-declaration

git rebase main

git switch main

git merge --ff-only fix/public-web-4-declaration

git switch fix/public-web-4-declaration

git rebase main

git switch main

git merge --no-ff fix/public-web-4-declaration

git switch main

git merge --squash fix/public-web-4-declaration