Skip to content
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

[Snyk] Security upgrade electron from 18.3.14 to 18.3.15 #11531

Merged
merged 1 commit into from Oct 4, 2022

Conversation

marcaaron
Copy link
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

merge advice

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Issue Breaking Change Exploit Maturity
high severity Use After Free
SNYK-JS-ELECTRON-3033161
No No Known Exploit
high severity Use After Free
SNYK-JS-ELECTRON-3033934
No No Known Exploit

Check the changes in this PR to ensure they won't cause issues with your project.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@marcaaron marcaaron requested a review from a team as a code owner October 3, 2022 10:20
@melvin-bot melvin-bot bot requested review from aldo-expensify and removed request for a team October 3, 2022 10:20
@marcaaron
Copy link
Contributor Author

I am so lost why is this PR created as me... 😕

@aldo-expensify
Copy link
Contributor

lol, it is not passing the "Contributor Checklist / checklist (pull_request)".

Copy link
Contributor

@aldo-expensify aldo-expensify left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No breaking changes: https://github.com/electron/electron/releases/tag/v18.3.15, This is a very small version increment, just fixing security issues.

Tested the desktop app and seems to be working fine.

@aldo-expensify aldo-expensify merged commit f2b2f07 into main Oct 4, 2022
@aldo-expensify aldo-expensify deleted the snyk-fix-44778d112f87fa5a6e1361a9c64d34c4 branch October 4, 2022 18:58
@melvin-bot melvin-bot bot added the Emergency label Oct 4, 2022
@melvin-bot
Copy link

melvin-bot bot commented Oct 4, 2022

@aldo-expensify looks like this was merged without passing tests. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

@aldo-expensify
Copy link
Contributor

No emergency: Snyk did a poor job and didn't check the Contributor's checklist

@OSBotify
Copy link
Contributor

OSBotify commented Oct 4, 2022

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@marcaaron
Copy link
Contributor Author

@aldo-expensify Well, I think the idea is that we would both go through the checklist in this case? Me as the author and you as the reviewer? But I'm not entirely sure. I don't even know why this PR was created. I sure as hell didn't create it.

@aldo-expensify
Copy link
Contributor

Not sure what Snyk uses to create PR's using our accounts, but this is not the first PR I get like this.

You may be right about the approach with the checklist, but I'm pretty sure that it would be just about checking everything because they are no changes in the code besides the dependencies. Regarding screenshots... a screenshot showing that the App is working could suffice (i mean for next time)?

@aldo-expensify
Copy link
Contributor

@marcaaron
Copy link
Contributor Author

pretty sure that it would be just about checking everything because they are no changes in the code besides the dependencies

yes, probably depends on the case though. If the dependency is related to Electron then I'd have a test to build the desktop app at the very least.

@aldo-expensify
Copy link
Contributor

Agreed, that's what I tested

@OSBotify
Copy link
Contributor

OSBotify commented Oct 6, 2022

🚀 Deployed to staging by @aldo-expensify in version: 1.2.12-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to production by @AndrewGable in version: 1.2.12-4 🚀

platform result
🤖 android 🤖 failure ❌
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 failure ❌
🕸 web 🕸 success ✅

smrutiparida pushed a commit to autosave-app/App that referenced this pull request Oct 13, 2022
…87fa5a6e1361a9c64d34c4

[Snyk] Security upgrade electron from 18.3.14 to 18.3.15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants