Skip to content
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.

Sign up for GitHub

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

Jump to bottom

upgrade Yarn to v4 #2245

Closed
1 of 2 tasks
turadg opened this issue Apr 25, 2024 · 0 comments · Fixed by #2222
Closed
1 of 2 tasks

upgrade Yarn to v4 #2245

turadg opened this issue Apr 25, 2024 · 0 comments · Fixed by #2222
Labels
enhancement New feature or request

Comments

@turadg
Copy link
Member

turadg commented Apr 25, 2024 •
edited
Loading

What is the Problem Being Solved?

Move from Yarn 1 to Yarn 4. Some advantages,

Description of the Design

Progress in #2222

Dependencies
Beta Give feedback
  1. ability to upgrade Lerna and Yarn in Endo without doing so in agoric-sdk Agoric/agoric-sdk#9288
    enhancement

Security Considerations

Scaling Considerations

Test Plan

Compatibility Considerations

Upgrade Considerations
@turadg turadg added the enhancement New feature or request label Apr 25, 2024
@turadg turadg mentioned this issue Apr 25, 2024
Merged
@michaelfig michaelfig mentioned this issue Aug 17, 2024
Merged
michaelfig added a commit that referenced this issue Aug 19, 2024
@michaelfig
chore: yarn up 'ses@workspace:^' '@endo/*@workspace:^' (#2416)
46ca503 
Refs: #2245 

## Description

Newer Yarn versions permit workspace-relative package references. This
PR uses them to reduce version churn in `yarn.lock` and the dependencies
sections of each `package.json`. A new version of Lerna supports this
feature, so upgrade that, too.

### Security Considerations

This PR helps improve the locality of inter-package dependencies by
avoiding the NPM repository except when publishing.

### Scaling Considerations

n/a

### Documentation Considerations

n/a

### Testing Considerations

Ran unit tests, followed `CONTRIBUTING.md` to verify that `lerna
publish` correctly replaces `workspace:` versions with semver when
publishing to NPM registry.

### Compatibility Considerations

n/a

### Upgrade Considerations

n/a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

upgrade to Yarn 4 endojs/endo
1 participant
@turadg