Skip to content

[CI] bump Node references from 12/14 to 14/16 - #32980

Closed
kelset wants to merge 1 commit into
mainfrom
chore/bump-node-to-16
Closed

kelset wants to merge 1 commit into
mainfrom
chore/bump-node-to-16

Conversation

@kelset

@kelset kelset commented Jan 27, 2022 •

Copy link
Copy Markdown
Contributor

Summary

Node 16 has been the LTS for quite some time now (Oct 2021), so this PR just wants to bring the RN OSS CI up to speed.

(I realized that this was needed while doing the same for macos microsoft#997)

Changelog

[General] [Changed] - Breaking: moving minimum version of Node expected to 14, and move CI to current LTS(16).

Test Plan

CI itself is the test 🤣 locally no significant changes were experienced.

@kelset
kelset requested a review from hramos as a code owner January 27, 2022 17:14
@facebook-github-bot facebook-github-bot added CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Contributor A React Native contributor. p: Microsoft Partner: Microsoft Partner Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team. labels Jan 27, 2022
@facebook-github-bot

Copy link
Copy Markdown
Contributor

@ShikaSD has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

Comment thread package.json
"repository": "github:facebook/react-native",
"engines": {
"node": ">=12"
"node": ">=14"

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.

This will create a warning or error for users of RN with Node 12. Is it okay to make the breaking change yet?

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.

Also, why 14 and not 16?

@kelset kelset Jan 28, 2022 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@NickGerleman I think it's ok to make it a breaking change, folks should be on current LTS (so 16).

@Saadnajmi it's 14 because on CircleCI we also have a job that tests against the previous LTS (14) hence why the requirement. You can see me bumping that nodeprevlts in this PR

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.

@NickGerleman I think it's ok to make it a breaking change, folks should be on current LTS (so 16).

Agree here. Plus the current Node version (non lts) is 17.
I think it's totally ok to drop Node 12 (maybe we should add a note in the Changelog for this).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

yeah let me change the changelog entry

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.

Seems like the changelog entry didn't sync properly, we might need to update this separately when building the changelog

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@ShikaSD interesting - is this because I changed the text of the PR body after the import process was started?

@ShikaSD ShikaSD Jan 28, 2022 •

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 we landed the previous version internally, so we didn't re-import the description

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

gotcha - makes sense.

ghost left a comment

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.

Change looks go to me 👍 You can disregard the internal failure as it's an unrelated warning (that gets exported as a error on Github Status).

@react-native-bot

ghost commented Jan 28, 2022

Copy link
Copy Markdown
Collaborator

This pull request was successfully merged by @kelset in f1488db.

When will my fix make it into a release? | Upcoming Releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Contributor A React Native contributor. Merged This PR has been merged. p: Microsoft Partner: Microsoft Partner Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants