-
Notifications
You must be signed in to change notification settings - Fork 2
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
RK-20397 - [DOB-490] fix old electron #379
Conversation
Github Enforcer opened Task: RK-20397 |
@@ -100,7 +100,7 @@ | |||
"aws-lambda": "^1.0.5", | |||
"copyfiles": "^2.3.0", | |||
"cross-env": "^5.2.0", | |||
"electron": "22.3.12", | |||
"electron": "26.6.10", |
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.
@FridmasterDyna
Did you make sure you addressed all breaking changes?
https://www.electronjs.org/docs/latest/breaking-changes#planned-breaking-api-changes-260
@@ -100,7 +100,7 @@ | |||
"aws-lambda": "^1.0.5", | |||
"copyfiles": "^2.3.0", | |||
"cross-env": "^5.2.0", | |||
"electron": "22.3.12", | |||
"electron": "26.6.10", |
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.
@FridmasterDyna
Also, this will auto update explorook for a few users and will break their epxplorook app
I recommend, at least, releasing a version that uses electron 22 and does not auto update, and inform those users they need to use that version
update electron version