Repository navigation
fix: use patched Node CA bundle in development and CI - #56
Merged
Merged
Conversation
Andarius
marked this pull request as ready for review
October 22, 2026 21:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Pin Node 22.23.4 in
.nvmrcafter the eMudhra/emSign CA incident, and use that file for every CI, Expo, and release job. This replaces the old Node 20 development runtime and vulnerable Node 22.21.0 release pin.Validated workflow YAML, all nine Node selectors, package JSON, Yarn 4.18.1 startup, and the actual Node 22.23.4 bundled CA fingerprints. Full native builds were not run; this changes tooling configuration only.