Repository navigation
fix(packaging): require standalone tls options artifact - #5494
KooshaPari wants to merge 1 commit into
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Harvest check: PR is still open and mergeable, and all current reported checks are green (semgrep-cloud-platform, semgrep, vitest fast-path, dast-smoke, both unit shards, Fast Quality Gates). Merge-ready from the current CI surface. |
|
Thanks @KooshaPari! This is now fully superseded. All three entries this PR adds to |
|
Current CI is green across Fast Quality Gates, both unit shards, Vitest, DAST, semgrep, and semgrep-cloud. This PR is merge-ready from the reported check surface. |
|
Merge-ready from the current check surface: Fast Quality Gates, both unit shards, Vitest, dast-smoke, semgrep, and semgrep-cloud are all passing. PR remains open and mergeable at last refresh. |
Summary
dist/tls-options.mjsin the npm pack artifact policytls-options.mjsin staged dist policyFixes #5452.
Why
server-ws.mjsimports./tls-options.mjsfrom the standalonedist/root. v3.8.41 already copies the sidecar during standalone assembly, but the publish policy did not requiredist/tls-options.mjs, allowing a tarball omission to ship.Validation
npm exec -- node --max-old-space-size=8192 --import tsx --import ./open-sse/utils/setupPolyfill.ts --import ./tests/_setup/isolateDataDir.ts --test tests/unit/pack-artifact-policy.test.tsreturnedokwhen polledgit diff --checkpassednpm run check:any-budget:t11returnedokwhen pollednpm run check:docs-syncreturnedokwhen polledNote:
npm run check:pack-policywas started but the local wrapper stalled innpm pack --dry-run; I interrupted it rather than claiming a full pack dry-run pass.