Repository navigation
test: Cover pnpm 12 multi-document lockfile settings - #14829
Closed
anthonyshew wants to merge 1 commit into
Closed
anthonyshew wants to merge 1 commit into
anthonyshew wants to merge 1 commit into
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
This branch was previously deployed
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
1 participant
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.
Description
Adds a
check-lockfilesfixture for #14827 using a lockfile generated by pnpm 12.11.2. The fixture has a leadingpackageManagerDependenciesdocument and a project document with all six resolution settings from the report. It prunes with--dockerand validates the frozen install inout/json.This is regression coverage only. #14423 already preserves these settings on the multi-document path. The new fixture reproduces the reported failure on published turbo 2.11.7, but passes on published 2.11.9 and the current source build. I could not reproduce the reported 2.11.9 failure.
minimumReleaseAge: 0lets pnpm's supply-chain check run without registry metadata during offline validation.Testing Instructions
Manually ran the same fixture against these binaries:
ERR_PNPM_LOCKFILE_CONFIG_MISMATCHforsettings.autoDedupe.out/json.out/json.To run against a local build, from
lockfile-tests:Also inspected the 2.11.9 output directly. Both
out/pnpm-lock.yamlandout/json/pnpm-lock.yamlretain both documents and all six settings, and omit the unselected workspace.