fix(cli): Set COREPACK_ENABLE_AUTO_PIN=0 during local pack of github packages #6529
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.
Different Corepack versions caused discrepancies in the addition of
packageManager
during Yarn installation, resulting in checksum changes and installation failures. This commit standardizes the behavior to avoid such errors.What's the problem this PR addresses?
issue
Error occurs because checksum changes with different corepack versions.
repro
When I generate yarn.lock with corepack0.18.0 and install with 0.29.4, I get the following error.
This is at least the environment in which it occurred to me.
I also think it probably occurs in any github url
why
The github pakcage is packed locally by running the
yarn pack
commandIt seems that corepack changes the checksum of the package by setting the packageManager field to package.json when this command is executed.
How did you fix it?
Set COREPACK_ENABLE_AUTO_PIN to not add packageManager field
Checklist