chore: fix other-node-versions by removing @8 specifier from corepack prepare pnpm#3912
Merged
JamesHenry merged 3 commits intolerna:mainfrom Nov 29, 2023
Merged
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 3bd0f79. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ⌛ The following targets are in progress
✅ Successfully ran 3 targetsSent with 💌 from NxCloud. |
2f4b05f to
846f136
Compare
846f136 to
da088ff
Compare
da088ff to
7b40ae3
Compare
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
2 participants
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.
The version of corepack shipped with node 18 seems to have issues resolving pnpm@8. This change fixes that issue by just specifying the latest version of pnpm instead.