Repository navigation
Support native pnpm in reproducible upstream qualification - #42
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pinned pnpm12 upstream installations stopped before execution because the installer assumed a Node
bin/pnpm.cjsentry. Resolve the pinned package's declared executable, admit bounded native ELF/Mach-O launches, verify its actual version, and recheck executable/manifest bytes and mode through final installed inventory. Node entries retain2MiB, native entries128MiB; corpus execution extends only the retained native-manager identity. Canonical output paths fix macOS/varversus/private/varreceipt parity. A dirty/incomplete clone cannot reach manager bootstrap.Adds a real-install CI proof for pnpm10.33.0 and12.3.4 on constructed fixtures: original frozen locks, actual project lifecycle, one native assertion per profile, post-run installed-byte verification, and retained raw evidence. The native fixture lock was generated by the actual pinned manager before fixture measurement and includes its self-manager dependencies.
Records a genuine unimport historical comparison at0efa812 versus exact prior source: both unchanged runtime suites report252 passed assertions; owner vue-tsc, standalone TypeScript and TestLore pass fixed source and preserve TS2554 in two prior repeats. This uses relocated existing dependencies, not a qualified fresh upstream installation. Native results cache changes are retained. Repeated names yield235 distinct keys; unique parameter identities and routing omissions remain unqualified. The owner already detects this type failure; no novel bug, speed, competitive or learning claim.
Validation:24/24 focused corpus/installer tests without skips; source/script syntax checks; actual pinned Node/native installations, lifecycle execution and independent native assertions on macOS. Independent review reconciled the historical raw reports, source/configuration/SDK bindings and case multisets. All12 hosted checks passed at f536f97. The complete hosted suite passed1413 actual cases across157 files, zero failures/skips/cancellations/todos, with actual Bun/Chromium. Final Linux Node24 native-manager proof and raw reconciliation passed. The production-only archive passed strict installed evidence and all210 members match committed bytes/modes. Earlier installation/fixture refusals remain retained; npm publication is separate and not completed.