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
Our version of Electron (20.3.8) is out of support 1 and Node v16 reaches EOL on 2. At the time of writing, Electron v24 is stable and supports Node v18.14. Updating both Node and Electron will require additional maintenance work with removing Nuxt as a dependency from Rancher Desktop; this task has been performed in Rancher Dashboard, so we should have a reference for this work.
Updating Electron and Node is necessary to ensure security and stability for Rancher Desktop, as well as to take advantage of new features and improvements in the latest versions. One enhancement that we will benefit from is in #4394.
Our version of Electron (20.3.8) is out of support 1 and Node v16 reaches EOL on 2. At the time of writing, Electron v24 is stable and supports Node v18.14. Updating both Node and Electron will require additional maintenance work with removing Nuxt as a dependency from Rancher Desktop; this task has been performed in Rancher Dashboard, so we should have a reference for this work.
Updating Electron and Node is necessary to ensure security and stability for Rancher Desktop, as well as to take advantage of new features and improvements in the latest versions. One enhancement that we will benefit from is in #4394.
✔️ Tasks
build(deps-dev): bump ts-loader from 8.4.0 to 9.2.1 #5310BrowserView.webContents.destroy()
withBrowserView.webContents.close()
#4394 (would be unblocked post Electron update)win-ca.ts
in Go for Electron Sandboxing Compatibility #5637registerHttpProtocol
®isterFileProtocol
are deprecated by Electron #5659🐛 Known Issues
Footnotes
https://www.electronjs.org/docs/latest/tutorial/electron-timelines#:~:text=Beginning%20in%20September%202021%20%28Electron%2015%29%2C%20the%20Electron,will%20continue%20until%20the%20release%20of%20Electron%2019. ↩
https://github.com/nodejs/release#release-schedule ↩
The text was updated successfully, but these errors were encountered: