-
Notifications
You must be signed in to change notification settings - Fork 72
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 to Yarn 4 #2222
upgrade to Yarn 4 #2222
Conversation
c415a8f
to
d860523
Compare
I’m interested in giving this a shot (and willing to suffer reverting it if it gets in the way of the sync cycle). I’m reluctantly willing to entertain dropping Windows from CI to unblock this (and reduce occurrences of flakey tests that Windows CI reveals more often than Linux.) Windows support is hard to get back once lost. May I ask for an Agoric SDK CI job pinned to this branch? |
We’ve seen a lot of EPIPE on write failures that are more common on Windows than Linux/Mac, though they do occur. For that reason along, it would be good to restore Windows CI when we track that issue down, but for now, the flakes are too hard to bear and also block us from upgrading yarn #2222 Tracking revert #2243
ca5e5c7
to
d8e1867
Compare
Integration probe Agoric/agoric-sdk#9285 |
Following https://yarnpkg.com/migration/guide: yarn set version berry yarn install
Yarn 4 is more strict
refs: #451 refs: #9209 ## Description We need agoric-sdk's integration tests to work with Endo running Yarn 4. #9285 tested against endojs/endo#2222. This PR is to land the necessary changes in master so the Endo PR can land without breaking SDK CI. This helps with #9209 and is a subset of #9286 , all that we need for Endo right now. ### Security Considerations none ### Scaling Considerations none, build time ### Documentation Considerations Nothing for SDK ### Testing Considerations CI ### Upgrade Considerations n/a
closes: #2245
refs: Agoric/agoric-sdk#451
refs: Agoric/ui-kit#105
Description
Move from Yarn 1 to Yarn 4. Some advantages,
However this defers workspace protocol until the publishing workflow can support it.
Security Considerations
This does a bulk update of
yarn.lock
. It was automated by Yarn 4.Scaling Considerations
n/a
Documentation Considerations
I reviewed
yarn
commands in *.md and I think they're all accurate.Testing Considerations
This could interact with the publishing pipeline. @kriskowal may want to push a draft before we merge. If problems are found, depending on the severity, we could follow up in a separate PR to land this sooner reduce merge conflicts.
This was failing on the Windows tests, something about corepack not taking effect. I don't know whether Windows is officially supported by Endo. We've since disabled them. #2243 is the issue restore.
Compatibility Considerations
Some CLI commands are slightly different. We are adopting it across the org so we have to adjust sometime.
Upgrade Considerations
n/a