[Snyk] Security upgrade sauce-connect-launcher from 1.2.7 to 1.3.2

[Exnadella]

User description

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• packages/wct-sauce/package.json
• packages/wct-sauce/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) npm:debug:20170905	506

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

---

PR Type

enhancement, dependencies

---

Description

• Updated sauce-connect-launcher dependency from version 1.2.7 to 1.3.2 to address security vulnerabilities.
• Updated agent-base and https-proxy-agent dependencies to newer versions for improved security.
• Updated debug dependency to version 4.3.6.
• These changes aim to fix vulnerabilities related to Regular Expression Denial of Service (ReDoS).

---

Changes walkthrough 📝

Relevant files

Dependencies

package-lock.json Update dependencies to address vulnerabilities                      packages/wct-sauce/package-lock.json Updated sauce-connect-launcher from version 1.2.7 to 1.3.2. Updated agent-base from version 4.3.0 to 6.0.2. Updated https-proxy-agent from version 2.2.4 to 5.0.1. Updated debug from version 3.2.6 to 4.3.6. +564/-577 package.json Upgrade sauce-connect-launcher dependency                                packages/wct-sauce/package.json Updated sauce-connect-launcher dependency to version 1.3.2. +1/-1

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[qodo-merge-pro]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[qodo-merge-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Security	Update the sauce-connect-launcher dependency to the latest version Update the sauce-connect-launcher dependency to the latest version (1.3.2) to address potential security vulnerabilities and benefit from the latest features and bug fixes. packages/wct-sauce/package.json [67] +"sauce-connect-launcher": "^1.3.2", - Apply this suggestion Suggestion importance[1-10]: 9 Why: The suggestion correctly identifies the update of the sauce-connect-launcher dependency to version 1.3.2, which is reflected in the PR code diff. This update is important for addressing potential security vulnerabilities and gaining access to the latest features and bug fixes. The suggestion is accurate and relevant to the changes made in the PR.	9

[qodo-merge-pro]

CI Failure Feedback 🧐

(Checks updated until commit 6afb244)

Action: test (ubuntu-latest)

Failed stage: Run npm run bootstrap [❌]

Failure summary: The action failed due to an error during the npm ci command execution: Several deprecated packages were detected, which might have contributed to the failure. The specific error message indicates that npm ci exited with code 1 in the 'wct-mocha' package. The error suggests checking the npm logs for more detailed information.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 556: npm WARN deprecated [email protected]: This module is no longer supported. 557: npm WARN deprecated [email protected]: This package is no longer supported. 558: npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 559: npm WARN deprecated [email protected]: This package is no longer supported. 560: npm WARN deprecated [email protected]: This package is no longer supported. 561: npm WARN deprecated @lerna/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 562: npm WARN deprecated @lerna/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 563: npm WARN deprecated @lerna/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 564: npm WARN deprecated @lerna/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. ... 738: npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links] 739: npm ERR! 740: npm ERR! aliases: clean-install, ic, install-clean, isntall-clean 741: npm ERR! 742: npm ERR! Run "npm help ci" for more info 743: npm ERR! A complete log of this run can be found in: 744: npm ERR! /home/runner/.npm/_logs/2024-09-05T15_53_02_304Z-debug-0.log 745: lerna ERR! npm ci exited 1 in 'wct-mocha' 746: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.