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

build: remove local yarn #19981

Merged
merged 1 commit into from
Nov 2, 2017
Merged

Conversation

gkalpak
Copy link
Member

@gkalpak gkalpak commented Oct 27, 2017

PR Checklist

PR Type

[x] Build related changes

What is the current behavior?

A local yarn is used in check-environment.js, which results in the --integrity check always failing (if dependencies were installed with the global yarn).

What is the new behavior?

The globally installed yarn is used in check-environment.js (and the --integrity does not fail unnecessarily).

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

This has already been fixed on 4.x.

@gkalpak gkalpak force-pushed the build-remove-local-yarn branch 2 times, most recently from 4911ddb to 8a566a7 Compare October 27, 2017 14:10
@gkalpak gkalpak added area: build & ci Related the build and CI infrastructure of the project action: review The PR is still awaiting reviews from at least one requested reviewer target: major This PR is targeted for the next major release labels Oct 27, 2017
@gkalpak gkalpak added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Oct 27, 2017
We use the globally installed yarn now. The local yarn was used in
`check-environment.js` only, which results in the `--integrity` check
always failing (if dependencies were installed with the global yarn).
@gkalpak gkalpak added target: patch This PR is targeted for the next patch release and removed target: major This PR is targeted for the next major release labels Nov 2, 2017
@vicb vicb merged commit 9975486 into angular:master Nov 2, 2017
vicb pushed a commit that referenced this pull request Nov 2, 2017
We use the globally installed yarn now. The local yarn was used in
`check-environment.js` only, which results in the `--integrity` check
always failing (if dependencies were installed with the global yarn).
@gkalpak gkalpak deleted the build-remove-local-yarn branch November 3, 2017 09:22
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project cla: yes target: patch This PR is targeted for the next patch release type: bug/fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants