-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: revert to electron@13 #143851
chore: revert to electron@13 #143851
Conversation
fd5ff02
to
3de7cd2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed I would suggest to do a full revert of the commits that went in first and then do selected changes on top that we want to keep. That would ensure we are not shipping a partial untested change.
I would suggest a PR composed of these commits:
- revert of the big E16 change
- revert of E16 associated changes (such as keytar update)
- 1 commit that selectively restores changes as needed
That would also make it much easier to review.
0f6beaf
to
bc6cd21
Compare
This reverts commit df645f1.
This reverts commit df645f1.
This reverts commit df645f1.
This reverts commit df645f1.
This reverts commit df645f1.
This reverts commit df645f1.
This reverts commit df645f1.
This reverts commit df645f1.
* chore: bump [email protected] * Revert "chore: revert to electron@13 (#143851)" This reverts commit df645f1. * chore: bump [email protected] * Revert "ci: fix build with latest node-gyp" This reverts commit c3e948a. * chore: revert ci changes for node v16 * chore: update yarn.lock * chore: bump [email protected]
Electron 16 update will be adopted in March 2022 milestone due to release blockers
PR contains following changes:
Will reopen the following issues once this PR gets merged,
#120431
#133820
#131714
#93615
#136787
#50386
#138721
#84453
fixed-in-electron-16 query