Repository navigation
chore(size): re-record the ledger on next @ 3b7ea81 after the 2026-10-29 batch - #4412
Conversation
…-29 batch Caps at CI brotli + 10 B rounded up to 0.01 KB, recorded minified = CI measured (next @ 3b7ea81, size job 123403325357). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
Size-Exception in the PR body: one batch re-record after the 2026-10-29 bug-fix batch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
Size (brotli, eager entry chunk)
Bundled with Rolldown (what Vite ships), brotli q11, decimal KB. A scenario fails only when it is over its brotli cap and its minified size is more than 20 B over the minified recorded with the cap; over the cap within that allowance is brotli layout noise and passes with a warning. Caps and their recorded minified in |
Coverage Report for CI Build 40864714159Coverage remained the same at 78.516%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Merging this PR will improve performance by 9.36%1 warning
Performance Changes
Tip Curious why performance improved? Comment Comparing Footnotes
|
|
The CodSpeed dip on Generated by Claude Code |
Before: the size check fails on every PR against
next. The 2026-10-29 bug-fix batch (#4401, #4397, #4383, #4393, #4406) merged without re-recording the ledger, as the maintainer asked, sonextsits over several caps and recorded minified sizes.After: every cap is CI brotli + 10 B rounded up to 0.01 KB, never lowered, and every recorded minified equals the CI measurement on
next@ 3b7ea81. The size check on new PRs measures growth from there.How: the numbers come from the size job on
next@ 3b7ea81 (job 123403325357). Each changedlimit:gets a dated ledger line inscripts/size/scenarios.js, and the frozen floors move infloor-caps.json. No source changes.The biggest moves, in brotli:
signals: + isPending/latest: 10.38 → 11.03 KB. Most of this is fix(signals): latest() opens no transaction for its verdict; its reader watches the seam (#4365) #4393 (+830 B minified over its base) plus fix(signals): an async memo over a verdict memo asks each question once #4397 and fix(signals): latest() of a memo born in a lane throws NotReady, not undefined (#4362, #4363, #4376) #4383.page: liveandlive + router: about +0.9 to +1.1 KB, for the same reason.app: compiled floor): 9.93 → 10.07 KB cap, measured at 10,059 B. That is over 10 KB.Size-Exception: one batch re-record after the 2026-10-29 bug-fix batch, which the maintainer asked for (2026-10-29). The frozen floors that move are the signals core floor (7.44 → 7.53 KB), the app render floor (9.75 → 9.88 KB), hydrating (18.49 → 18.80 KB), page base (33.37 → 33.78 KB) and page live (37.75 → 38.67 KB). Each one is the CI measurement on next @ 3b7ea81 + 10 B.
Generated by Claude Code