Skip to content

build: update node and yarn to latest stable versions #17474

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

Merged
merged 1 commit into from
Oct 24, 2019

Conversation

devversion
Copy link
Member

@devversion devversion commented Oct 23, 2019

Some CI jobs currently fail because db283f1 removed
Node v11 from the supported node versions. Some of CI jobs use Node v11 though, so they
currently fail. e.g. https://circleci.com/gh/angular/components/89692.

In order to fix this, we ensure that we use consistent versions. For Node, we use the current
active LTS version (v12). And for Yarn, we use the latest stable yarn version.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 23, 2019
@devversion devversion force-pushed the build/update-yarn-node branch 2 times, most recently from 4e38a5e to 12f06d5 Compare October 23, 2019 08:18
@devversion devversion marked this pull request as ready for review October 23, 2019 08:25
@devversion devversion requested review from jelbourn and a team as code owners October 23, 2019 08:25
@devversion devversion added pr: merge safe target: major This PR is targeted for the next major release labels Oct 23, 2019
@devversion devversion requested a review from crisbeto as a code owner October 23, 2019 12:16
@devversion
Copy link
Member Author

For reference: a few goldens had to be updated because the method overloads are now sorted based on their declaration order. This previously was not the case because Array.sort was not stable for more than 10 elements. see: https://bugs.chromium.org/p/v8/issues/detail?id=90

Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

@devversion devversion force-pushed the build/update-yarn-node branch 2 times, most recently from e730954 to d8d6785 Compare October 23, 2019 16:31
@devversion
Copy link
Member Author

@josephperrott Feedback addressed. Please have another look

Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

Some CI jobs currently fail because db283f1 removed
Node v11 from the supported node versions. Some of CI jobs use Node V11 though, so they
currently fail. e.g. https://circleci.com/gh/angular/components/89692.

In order to fix this, we ensure that we use consistent versions. For Node, we use the current
active LTS version (v12). And for Yarn, we use the latest stable yarn version.
@devversion devversion force-pushed the build/update-yarn-node branch from d8d6785 to f0e5608 Compare October 23, 2019 18:40
@devversion devversion added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Oct 24, 2019
@mmalerba mmalerba merged commit 4fab30f into angular:master Oct 24, 2019
@Splaktar
Copy link
Contributor

How is requiring NodeJS 12 working with relation to the fact that Gulp 3 doesn't work with it?

We're still on "gulp": "^3.9.1",.

@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 Nov 28, 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 cla: yes PR author has agreed to Google's Contributor License Agreement target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants