-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Electron 28 has reached end-of-life #11378
Comments
This is a real problem creating issues at downstream. Fix of |
Indeed, several package managers are blocked by this. |
Hi There! 👋 We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help! If the issue has been resolved or is no longer relevant, that's great news! 🎉 Access additional Logseq 🚀 resources:
Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too! |
Extremely relevant, Logseq really needs to get on a supported version of Electron. |
It seems that #11620 upgraded Electron to v31.7.5, which, unfortunately, will reach EOL in less than a month. Since this issue is technically resolved, I'm going to close it. However, I think it's likely that we'll encounter an EOL Electron again, so I'm going to point to #11644 for future tracking. |
Search first
What Happened?
Logseq currently uses Electron 28, which is no longer supported by upstream since last week (June 11). It would be a good idea to switch to a newer version of Electron. The release timelines can be found here. I'd suggest at least Electron 30 since Electron 29 will also reach EOL in August, which is not too far from now.
Reproduce the Bug
N/A
Expected Behavior
No response
Screenshots
No response
Desktop or Mobile Platform Information
No response
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: