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.

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

fix(core): use the current CLI to prepare external Yarn classic projects #4682

Merged
merged 3 commits into from
Aug 4, 2022

Conversation

merceyz
Copy link
Member

@merceyz merceyz commented Jul 27, 2022

What's the problem this PR addresses?

  • When Corepack is enabled and the default version of Yarn is set to classic the output of preparing an external Yarn classic project (installing a git dependency) wont match that of a system without Corepack.
  • When yarn set version classic is run it updates the Manifest to contain a packageManager field with the latest Yarn version which causes the results to change depending on when it runs.

How did you fix it?

  • Explicitly use the current CLI to fetch Yarn classic.
  • Revert any changes done to the Manifest by yarn set version.

Checklist

  • I have read the Contributing Guide.
  • I have set the packages that need to be released for my changes to be effective.
  • I will check that all automated PR checks pass before the PR gets reviewed.

@merceyz merceyz requested a review from arcanis as a code owner July 27, 2022 12:32
rally25rs
rally25rs previously approved these changes Jul 27, 2022
Copy link
Contributor

@rally25rs rally25rs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This did seem to resolve an issue of differing github dependency checksums I was seeing between 2 machines. The package.json of the cloned dependency repo was being modified differently depending on which yarn was being called to run these commands to prepare the dependency.

With this PR they started generating the same checksum.

@arcanis arcanis merged commit 635ed55 into master Aug 4, 2022
@arcanis arcanis deleted the merceyz/fix/prepare-external-classic branch August 4, 2022 11:58
merceyz added a commit that referenced this pull request Aug 19, 2022
…cts (#4682)

* fix(core): use the current CLI to prepare external Yarn classic projects

* fix(core): revert changes made to the Manifest by `set version`

* fix: add `--yarn-path`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants