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

chore: upgrade to Node.js v14.9.0 #25249

Merged
merged 41 commits into from
Sep 17, 2020
Merged

chore: upgrade to Node.js v14.9.0 #25249

merged 41 commits into from
Sep 17, 2020

Conversation

codebytere
Copy link
Member

@codebytere codebytere commented Sep 1, 2020

Description of Change

Upgrade Node.js to v14.9.0

Checklist

Release Notes

Notes: Upgraded Node.js to v14.9.0.

@electron-cation electron-cation bot added the new-pr 🌱 PR opened in the last 24 hours label Sep 1, 2020
@codebytere codebytere changed the title [wip] chore: upgrade to Nodej.s v14.9.0 [wip] chore: upgrade to Node.js v14.9.0 Sep 1, 2020
@codebytere codebytere force-pushed the nodejs-v14 branch 3 times, most recently from 17156aa to 5b5c169 Compare September 2, 2020 04:09
@electron-cation electron-cation bot removed the new-pr 🌱 PR opened in the last 24 hours label Sep 2, 2020
@codebytere codebytere force-pushed the nodejs-v14 branch 13 times, most recently from 182dd3f to 799c17e Compare September 4, 2020 17:06
@codebytere codebytere changed the title [wip] chore: upgrade to Node.js v14.9.0 chore: upgrade to Node.js v14.9.0 Sep 4, 2020
@codebytere codebytere marked this pull request as ready for review September 4, 2020 19:00
@codebytere codebytere requested review from a team as code owners September 4, 2020 19:00
@codebytere
Copy link
Member Author

codebytere commented Sep 4, 2020

This PR is ready for initial review - arm CI is experiencing some Struggles™️ so i'll sort those out before looking to land this.

@codebytere codebytere added the semver/major incompatible API changes label Sep 4, 2020
@codebytere codebytere force-pushed the nodejs-v14 branch 4 times, most recently from 79a00ae to a3a43b9 Compare September 14, 2020 23:19
Copy link
Member

@MarshallOfSound MarshallOfSound left a comment

Choose a reason for hiding this comment

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

Blocking on the types problem as that will be a big regression for folks if some types stop being auto-inferred 🤔

Happy to help look into it once I'm not fighting nan in the upgrades branch

@codebytere
Copy link
Member Author

@MarshallOfSound it's been resolved - just working on verifying one last thing with the net specs atm

@codebytere codebytere force-pushed the nodejs-v14 branch 2 times, most recently from 015c1de to 73ba23b Compare September 17, 2020 05:39
Copy link
Member

@nornagon nornagon left a comment

Choose a reason for hiding this comment

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

lgtm with nits

lib/browser/api/net.ts Show resolved Hide resolved
spec-main/api-context-bridge-spec.ts Show resolved Hide resolved
spec-main/api-ipc-spec.ts Outdated Show resolved Hide resolved
spec-main/api-net-spec.ts Outdated Show resolved Hide resolved
@codebytere codebytere merged commit 77038b7 into master Sep 17, 2020
@release-clerk
Copy link

release-clerk bot commented Sep 17, 2020

Release Notes Persisted

Upgraded Node.js to v14.9.0.

@linonetwo
Copy link

Is this added to the v11 beta? This fixes an important issue about worker_thread and we hope we can adapt this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver/major incompatible API changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants