Repository navigation
chore: a seat-shadow build can't be published; the carve brief points at its stop - #4448
Conversation
… at its stop Follow-ups from #4438's review. - verify-release-artifacts.mjs (run by release.mjs before anything is published) fails when a fixed package's tarball carries `__SEAT_SHADOW__`, the mark a SIGNALS_TEST_DEFINE=true build leaves in @solidjs/signals' dist/dev-shared.js. A shadow build is a test build (rollup.config.js: "never for measuring or publishing"). - reader-seat-brief.md §4 says the swap stopped and points at reader-seat-rebuild.md §8, which supersedes it. Co-Authored-By: Claude Opus 5.5 <[email protected]> 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 |
…-x1ore2-seat-release-guard
Coverage Report for CI Build 41026749382Coverage remained the same at 78.1%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Merging this PR will not alter performance1 warning
Comparing Footnotes
|
Summary
Before: a
@solidjs/signalsdist built withSIGNALS_TEST_DEFINE=truecarries the reader-seat shadow, about 1.7 KB of__SEAT_SHADOW__andshadowReadindist/dev-shared.js. Nothing in the release path noticed, andtests/dist-artifacts.test.tspasses on such a build. Separately,documentation/plans/reader-seat-brief.md§4 still describes "rebuild beside, then swap" as the plan, with no sign that the swap stopped.After:
scripts/verify-release-artifacts.mjsfails a release whose tarball carries__SEAT_SHADOW__. release.mjs runs this script before it publishes anything. Brief §4 opens with a stop note pointing atreader-seat-rebuild.md§8, which records the S1 result and supersedes §4.These are follow-ups from #4438's review.
How
.js/.mjs/.cjsfile in each fixed package's dry-run tarball list and looks for__SEAT_SHADOW__, the global the shadow installs its report sink on (core/seat.ts).dist-artifacts.test.tsalone, because the differential workflow runs the suites on a shadow build on purpose.How did you test this change?
I built
@solidjs/signalstwice and ran the check's filter over thenpm pack --dry-run --jsonfile list:SIGNALS_TEST_DEFINE=true, it flagsdist/dev-shared.js.The full script's
npm publish --dry-runstep can't run locally, because rc.20 is already on npm and the local npm prints a different--jsonshape. The release workflow runs it on the version-bumped commit. Prettier is clean on both files.Generated by Claude Code