Skip to content

build: bump yarn requirement to 1.17.3#32344

Closed
josephperrott wants to merge 1 commit into
angular:masterfrom
josephperrott:yarn-update
Closed

build: bump yarn requirement to 1.17.3#32344
josephperrott wants to merge 1 commit into
angular:masterfrom
josephperrott:yarn-update

Conversation

@josephperrott
Copy link
Copy Markdown
Member

No description provided.

@josephperrott josephperrott added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release labels Aug 27, 2019
@josephperrott josephperrott requested review from a team August 27, 2019 14:44
@ngbot ngbot Bot added this to the needsTriage milestone Aug 27, 2019
Copy link
Copy Markdown
Member

@gkalpak gkalpak left a comment

Choose a reason for hiding this comment

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

Shouldn't you also update CI yarn to 1.17.3+?

@josephperrott josephperrott force-pushed the yarn-update branch 2 times, most recently from 58b723a to 99365f4 Compare August 27, 2019 17:13
@josephperrott
Copy link
Copy Markdown
Member Author

@gkalpak Correct, done.

Comment thread WORKSPACE
@@ -73,7 +76,7 @@ node_repositories(
# It possible that versions of yarn past 1.13.0 do not have this issue, however, before
# advancing this version we need to test manually on Windows that the above error does not
# happen as the issue is not caught by CI.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Have you checked whether this issue is fixed on Windows? If it is, we should remove the comment. If it isn't, then we have a problem 😁
(I could check, but I don't know how to reproduce the issue - I looked at the related issue, but didn't find anything.)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think you could repro on windows by just doing two yarn bazel build ... in a row? @gregmagolan might remember.

mhevery pushed a commit that referenced this pull request Aug 29, 2019
@mhevery mhevery closed this in 4b12511 Aug 29, 2019
@josephperrott
Copy link
Copy Markdown
Member Author

@devversion did some builds with it and didn't see any issues. Though we didn't know how to specifically repro it so we couldn't be entirely sure. From my understanding he did multiple yarn bazel builds

sabeersulaiman pushed a commit to sabeersulaiman/angular that referenced this pull request Sep 6, 2019
@angular-automatic-lock-bot
Copy link
Copy Markdown

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 29, 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants