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] Upgrade @electron/remote from 2.0.7 to 2.0.8 #684

Merged
merged 1 commit into from
May 1, 2022

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade @electron/remote from 2.0.7 to 2.0.8.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released a month ago, on 2022-03-15.

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

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade @electron/remote from 2.0.7 to 2.0.8.

See this package in npm:


See this project in Snyk:
https://app.snyk.io/org/th-ch/project/81809c53-bb7b-46b9-a0d7-806d45d74ac6?utm_source=github&utm_medium=referral&page=upgrade-pr
@Araxeus
Copy link
Collaborator

Araxeus commented Apr 10, 2022

please close in favor of #605

@th-ch th-ch merged commit 7b3a767 into master May 1, 2022
@th-ch th-ch deleted the snyk-upgrade-82480fa720c2520dafdd84fa5f54d19b branch May 1, 2022 19:54
@th-ch
Copy link
Owner

th-ch commented May 1, 2022

Ah just saw the comment - this PR should not create any issues (so not reverting for now) but will be superseded by #605 indeed

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.

3 participants