[Snyk] Upgrade electron-serve from 1.2.0 to 1.3.0

[melvin-bot]

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

Snyk has created this PR to upgrade electron-serve from 1.2.0 to 1.3.0.

ℹ️ 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 21 days ago, on 2024-01-22.

Release notes

Package name: electron-serve

• 1.3.0 - 2024-01-22
  
  • Support search parameteres in the loadUrl method (#37) 7ae7d43
  • Support loading an HTML file with a custom name (#36) c307a57

  v1.2.0...v1.3.0

• 1.2.0 - 2023-11-01
  
  • Add hostname option (#35) 8dd370b

  v1.1.0...v1.2.0

from electron-serve GitHub release notes

Commit messages

Package name: electron-serve

• e7115ec 1.3.0
• 9aa64ca Meta tweaks
• 7ae7d43 Support search parameteres in the `loadUrl` method (Have the ability to add comments now #37)
• c307a57 Support loading an HTML file with a custom name (Fix dev/prod issues by splitting up webpack configs #36)

Compare

---

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

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01dadc0abcbe141ed3
• Upwork Job ID: 1757105373386362880
• Last Price Increase: 2024-02-12

[melvin-bot]

This is a Snyk issue. Snyk is a tool that automatically tracks our repositories' dependencies and reports associated security vulnerabilities. It also automatically create PRs to fix these vulnerabilities.

    C+: Please follow these steps to test the linked PR before running through the reviewer checklist:
    - [ ] The first step is to understand the PR: what dependency is it upgrading, for which vulnerability, how it impacts our product & end users.
    - [ ] If the issue is not worth fixing, please add your reasoning in the issue and have the internal engineer review it.
    - [ ] Check the change log (which should be included in the PR description) to see all changes. We want to identify any breaking changes. If it is a minor version bump, it's unlikely that there are any breaking changes.
    - [ ] Test our feature(s) that make use of this package. If it does not work, we should understand what broke it. It is also a good idea to check our main flows to make sure they are not broken that you can add in the checklist screenshots/videos.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01dadc0abcbe141ed3

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @c3024 (Internal)

[c3024]

@mountiny Could you close this? The PR #36356 has already been merged. Thanks.