-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Yarn 3.2.1 to 4.0.0-rc.9+ #672
Conversation
Check
|
Yarn 4.0.0-rc.9 yarn set version canary
yarn install yarn --check-resolutions
➤ YN0000: ┌ Resolution step
➤ YN0078: │ Invalid resolution node-forge@npm:^0.10.0 → npm:1.2.1 (yarn why: ... RN Flipper)
➤ YN0000: └ Completed
➤ YN0000: Failed with errors in 0s 137ms revert yarn.lock (v4 -> v3) revert (old v3) resolution commit yarn install (regen v4 lockfile) yarn --check-resolutions
➤ YN0000: ┌ Resolution step
➤ YN0078: │ Invalid resolution prismjs@npm:~1.17.0 → npm:1.26.0 (yarn why: ... @storybook)
➤ YN0000: └ Completed
➤ YN0000: Failed with errors in 0s 137ms
|
edit: ok only few shouldn't be necessary to upg Yarn v3 -> v4 🤔 temp: revert commits in order solution: difficult w/o commit hist since lockfile snapshot overwritten 5x hack: delete yarn lockfile to remove Yarn v3 resolutions, then re-create with Yarn v4? but resolutions lost on devDeps |
follow-up attempt here: #846 |
Raised in Followed up in |
Only issue in Linux CI, macOS 13b locally is fine
Latest checked: rc.14
Ubuntu2204 (20220605.1)
Similar on macOS Monterey 12.5 Beta
yarn install
yarn --check-resolutions
Next step
--check-resolutions
yarnpkg/berry#4302 (comment)Follow-up
Still need to undo resolutions
Close: #671