Bump Electron to 13.5.1 to fix SSL certificate problem with Let's Encrypt #2996
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
|
Let me know if there's anything else to be done in this PR. It should be merged as soon as possible. |
|
Closed in #2999 |
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.
Hi, since yesterday, all apps around the world suffered a problem with Let's Encrypt; suddenly Electron couldn't recognize Let's Encrypt as a secure certificate, and led to errors like "Certificate has expired".
It started happened to me as well.
Here's the PR that the Electron team created yesterday, which's merged into 13.5.1:
electron/electron#31216
More info of users having the problem:
electron/electron#31212