Update Electron to 13.5.1 to fix LetsEncrypt CERT_HAS_EXPIRED issues #1749
Conversation
This file contains 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
This fixes issues with LetsEncrypt certificates
|
|
|
Works for me! 🍾 (Tested on OSX, I guess we'll know soon enough if this breaks on windows for some reason.) |
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.
This fixes issues with LetsEncrypt certificates that manifest themselves in errors like:
electron/electron#31212 describes the issue that is fixed by electron/electron#31213.
The Electron v13 release that has this fix is v13.5.1: https://releases.electronjs.org/release/v13.5.1