Downgrade yarn3 to yarn1 #99
Merged
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
zemyblue
reviewed
Jul 31, 2023
|
because wasm files are untracked as lfs and track again as normal file. |
zemyblue
previously approved these changes
Jul 31, 2023
jaeseung-bae
reviewed
Aug 1, 2023
zemyblue
approved these changes
Aug 1, 2023
jaeseung-bae
approved these changes
Aug 1, 2023
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.
Description
While yarn3 have all the dependencies, we need to upload all the dependencies to lfs storage.
but currently lfs storage's bandwidth exceeded free plan so we are going to change not to use lfs storage.
In this PR, yarn3 change to yarn1 not to contain all the dependencies and untrack all the lfs files.
Motivation and context
How has this been tested?
Screenshots (if appropriate):
Checklist:
CHANGELOG.md.