#55041: chore: rework BoringSSL with Node.js incompatibilities patch
Requested by David Babenko-Sanders · Slack thread
Description of Change
Manually backport #55037. See that PR for details.
CC @dsanders11
The cherry-pick conflicted only in the generated index and hunk headers of the node patches, because this branch's node patch series differs from main's (this branch also lacks main's fix_use_a_dedicated_cppheappointertag_for_cppgc_wrappables.patch, and src_backport_the_perfetto_trace_agent.patch is src_add_perfetto_trace_agent.patch here), so I rebuilt them by applying this branch's series plus the change to Node.js v24.22.0 and re-exporting with script/git-export-patches, which gives the same Node.js source delta as on main.
Checklist
- I have built and tested this change
- I have filled out the PR description
- I have reviewed and verified the changes
-
npm testpasses - PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.
🤖 Generated with Claude Code
https://claude.ai/code/session_01FEtfbdwkKabsmYWAF8Sqsw
Release Notes
Notes: none
Generated by Claude Code
Backport Information
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron