chore: remove upstreamed Node.js patches - #52694
Conversation
|
💖 Thanks for opening this pull request! 💖 Semantic PR titlesWe use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix. Examples of commit messages with semantic prefixes:
Commit signingThis repo enforces commit signatures for all incoming PRs. PR tipsThings that will help get your PR across the finish line:
We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can. |
|
For more information on signing commits, see GitHub's documentation on Telling Git about your signing key. |
Node.js now enables Float16Array on the global object and includes <cstdlib> in builtin_info.cc. The corresponding Electron patches are therefore no-ops on Node.js v24.18.1. Remove both patches and re-export the Node.js patch series. Refs: nodejs/node#58154 Refs: nodejs/node#63001
|
@jkleinsc Sorry,I just don't notice that requirement |
|
Congrats on merging your first pull request! 🎉🎉🎉 |
|
No Release Notes |
|
I have automatically backported this PR to "44-x-y", please check out #52728 |
Description of Change
Node.js now enables Float16Array on the global object and includes in builtin_info.cc. The corresponding Electron patches are therefore no-ops on Node.js v24.18.1.
Remove both patches and re-export the Node.js patch series.
Refs: nodejs/node#58154
Refs: nodejs/node#63001
Checklist
Release Notes
Notes: None