Make burner's package fit the module registry: four compiled bun binaries gzip to 146.6 MB against a 100 MiB publish limit #1368

New issue

Open

opened 2026-09-10 22:34:59 +00:00 by forgejo-admin · 0 comments

forgejo-admin commented

2026-09-10 22:34:59 +00:00

Owner

burner cannot be published to the module registry. Its build compiles four binaries with bun build --compile, a server and a worker for linux-x64 and linux-arm64, and each one embeds the whole bun runtime. Measured on 2026-09-10 with bun 1.4.2, the version CI uses: about 81 MB each, 325 MiB raw, and the four alone gzip to 146.6 MB. The registry caps a publish at 100 MiB, so no release can publish burner, and until something changes every release sweep fails on it.

Scope

modules/burner/manifest.yml, the build.command block (lines 132-155 on main at 4657c542): four bun build --compile invocations and four artifacts.
packages/registry-server/src/server.ts:42, MAX_PUBLISH_BYTES = 100 * 1024 * 1024. Bun.serve's default request limit (128 MiB) sits in front of it.
Seed instance: release run 6705, 2026-09-10 about 22:04Z, burner@0.1.1+1. burner landed on main on 2026-09-09 (30f5b35b, 52f6ed76, 05681ae8) and has never been published.
The ways out, for the module's owner and peba to choose between:
- One binary per architecture with a server/worker switch halves the package.
- Shipping the JS and running it on the host's bun makes it small.
- Raising the registry's limit (both its own cap and Bun's request limit) is a registry-server change plus a celilo-registry redeploy, and it makes a 140 MiB module normal.

Acceptance

burner's packed .netapp is under the registry's publish limit, measured on the package, not estimated.
burner publishes through release.yml and appears in the registry's index.
Recurrence gate: module packaging fails loudly, naming the module, the size and the limit, when a package exceeds the registry's publish limit. Today the failure first appears as an upload error in the middle of a release.

The registry client error issue, filed alongside this one. It hid this cause.
The release module sweep issue, filed alongside this one. It is why this one module blocked the whole release.
celilo PR #1251 (jem's Burner PR).

burner cannot be published to the module registry. Its build compiles four binaries with `bun build --compile`, a server and a worker for linux-x64 and linux-arm64, and each one embeds the whole bun runtime. Measured on 2026-09-10 with bun 1.4.2, the version CI uses: about 81 MB each, 325 MiB raw, and the four alone gzip to 146.6 MB. The registry caps a publish at 100 MiB, so no release can publish burner, and until something changes every release sweep fails on it. ## Scope - `modules/burner/manifest.yml`, the `build.command` block (lines 132-155 on main at 4657c542): four `bun build --compile` invocations and four artifacts. - `packages/registry-server/src/server.ts:42`, `MAX_PUBLISH_BYTES = 100 * 1024 * 1024`. Bun.serve's default request limit (128 MiB) sits in front of it. - Seed instance: release run 6705, 2026-09-10 about 22:04Z, burner@0.1.1+1. burner landed on main on 2026-09-09 (30f5b35b, 52f6ed76, 05681ae8) and has never been published. - The ways out, for the module's owner and peba to choose between: - One binary per architecture with a server/worker switch halves the package. - Shipping the JS and running it on the host's bun makes it small. - Raising the registry's limit (both its own cap and Bun's request limit) is a registry-server change plus a celilo-registry redeploy, and it makes a 140 MiB module normal. ## Acceptance - [ ] burner's packed `.netapp` is under the registry's publish limit, measured on the package, not estimated. - [ ] burner publishes through `release.yml` and appears in the registry's index. - [ ] Recurrence gate: module packaging fails loudly, naming the module, the size and the limit, when a package exceeds the registry's publish limit. Today the failure first appears as an upload error in the middle of a release. ## Related - The registry client error issue, filed alongside this one. It hid this cause. - The release module sweep issue, filed alongside this one. It is why this one module blocked the whole release. - celilo PR #1251 (jem's Burner PR).

forgejo-admin added the

severity:high

category:bug

labels

2026-09-10 22:34:59 +00:00

forgejo-admin referenced this issue from a commit

2026-09-10 22:47:23 +00:00

feat(publish): --skip-module leaves a module out of the registry sweep (celilo#1368)

forgejo-admin referenced this issue from a commit

2026-09-10 23:01:30 +00:00

feat(publish): --skip-module leaves a module out of the registry sweep (celilo#1368)