You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see you tried migrating from node 16 to address security issues.
Here is the thing, we use electron 22, which is based on node 16, so this change might not be enough to address whatever it is you are trying to address.
However, upgrading electron is problematic, because the major we use is the last one to support windows 7 and 8 (and win server 2012) and some mac os versions.
My recommendation is as such:
Add a check if a user's os is at least win 10/win server 2016 (or 19? Check win 10 equiv in server) or oldest supported macos before checking for auto update version
Release this as a minor patch so that everyone that should stop getting auto updates due to an old os gets the patch.
Then, publish a new version with a newer electron version to make sure the priject uses node 18 :)
The text was updated successfully, but these errors were encountered:
Hey guys, it is me :).
I see you tried migrating from node 16 to address security issues.
Here is the thing, we use electron 22, which is based on node 16, so this change might not be enough to address whatever it is you are trying to address.
However, upgrading electron is problematic, because the major we use is the last one to support windows 7 and 8 (and win server 2012) and some mac os versions.
My recommendation is as such:
Add a check if a user's os is at least win 10/win server 2016 (or 19? Check win 10 equiv in server) or oldest supported macos before checking for auto update version
Release this as a minor patch so that everyone that should stop getting auto updates due to an old os gets the patch.
Then, publish a new version with a newer electron version to make sure the priject uses node 18 :)
The text was updated successfully, but these errors were encountered: