fix(corepack): Manually install newer version of corepack to avoid key id mismatch #523
Conversation
This file contains 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
|
Does setting COREPACK_INTEGRITY_KEYS=0 also work? |
|
Yeah setting COREPACK_INTEGRITY_KEYS=0 does work, but that seems like it leaves you open to security vulnerabilities. |
|
Up to you which route you want to take, I'm happy to update this PR when you make a decision |
|
@viceice should we merge this temporarily? |
|
closing as we now use pnpm setup action |
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.
nodejs/corepack#612 (comment)
This temporary fix is required to get corepack working again until the next release of node