Repository navigation
Update Electron and undici security patches - #2
Merged
Merged
Conversation
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.
The packaged Electron runtime was affected by the pointer-lock frame attribution and eMudhra certificate advisories. The lockfile also retained an undici version with three network handling advisories.
Update the pinned Electron runtime from 44.4.5 to the first safe 44.x release, 44.9.1, and undici from 7.30.0 to 7.30.1. The Windows packaging workflow reads this pinned runtime version and verifies its official checksum.
Validation: clean npm ci, npm audit reports 0 vulnerabilities (previously 2 high dependency findings), 29 core tests passed, and 23 real Electron window tests passed without renderer errors. GitHub Actions also checks Linux/Windows interactions and builds the Windows package.