You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(release): the ubuntu smoke never hard-fails a mismatched-platform tarball, and two stale test citations
MEASURED on the real p9a/platform CI run: npm treats every explicitly-named install argument as
REQUIRED regardless of the wrapper's own optionalDependencies, so a mismatched-platform tarball
(darwin-arm64 on an ubuntu runner) refused the WHOLE offline install with EBADPLATFORM -- not just
its own package. smoke-installed.ts now excludes a bin-only package from the npm install command
line when its os/cpu does not match the current host, answering its check as a SKIP without ever
installing or spawning it.
Also: the platform tarball ships no bin/ entry at all on a host that never built the binary (an
empty directory is never packed), so the pack test's bin/-presence assertion is now host-gated; and
two WS-13 citations in packages/conformance still quoted release-pack.test.ts's/build-packages.test.ts's
pre-rename test titles.
bullet: "the publish pipeline packs, scans the TARBALL's contents, and imports every publishable package's every declared exports subpath from a real installed tarball",
959
959
status: "new",
960
960
citations: [
961
-
{file: `${SCRIPTS}/release-pack.test.ts`,testName: "the publishable set is exactly R-7-1's five packages -- excludes the private runtime and the unpublished (R-7-2) platform package"},
961
+
{file: `${SCRIPTS}/release-pack.test.ts`,testName: "the publishable set is exactly R-7-1's five JS packages PLUS the darwin-arm64 platform package (P9a-3) -- excludes only the private runtime"},
962
962
{file: `${SCRIPTS}/release-pack.test.ts`,testName: "catches all seven categories in one pass over one fixture"},
963
963
{file: `${SCRIPTS}/release-pack.test.ts`,testName: "P7a fix wave (item 9): NO tarball ships a test file -- verified via `tar -tzf`, independently of the scanner"},
964
964
{file: `${SCRIPTS}/smoke-installed.test.ts`,testName: "every publishable package's OWN exports map is fully covered -- no subpath silently skipped"},
965
965
{file: `${SCRIPTS}/smoke-installed.test.ts`,testName: "every target imports cleanly -- this is the exact check that would have caught review r1's two Criticals"},
966
-
{file: `${SCRIPTS}/build-packages.test.ts`,testName: "every entry emits BOTH a .js and a .d.ts, at the path its manifest condition names"},
966
+
{file: `${SCRIPTS}/build-packages.test.ts`,testName: "every entry emits BOTH a .js and a .d.ts, at the path its manifest condition names (bin-only packages emit none)"},
967
967
],
968
968
note: "The last citation is the fix wave's item 1 (R-7a-16 reversed): every manifest now points its `default` condition at a compiled emit, so `pack-smoke-node18` is a BLOCKING gate rather than the advisory carry it shipped as. The Node leg asserts what each package DECLARES through `engines` -- `@yanlinglabs/winter-provider-conformance` is Bun-only by construction (`Bun.serve` loopback fakes) and declares `engines.bun` alone.",
0 commit comments