[Snyk] Security upgrade http-proxy-middleware from 0.17.4 to 0.18.0

[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/polyserve/package.json
• packages/polyserve/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Validation Bypass SNYK-JS-KINDOF-537849	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:

🦉 Validation Bypass

---

PR Type

enhancement, dependencies

---

Description

• Upgraded the http-proxy-middleware dependency from version 0.17.2 to 0.18.0 in package.json to address security vulnerabilities.
• Updated package-lock.json to reflect the changes in http-proxy-middleware version.
• This upgrade fixes the vulnerability identified as [SNYK-JS-KINDOF-537849].

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Upgrade http-proxy-middleware dependency to address vulnerabilities packages/polyserve/package.json Upgraded http-proxy-middleware from version 0.17.2 to 0.18.0. +1/-1      package-lock.json Update package-lock.json for dependency upgrade                    packages/polyserve/package-lock.json Updated lock file to reflect the upgrade of http-proxy-middleware to version 0.18.0. +6321/-5429
Additional files (token-limit)	package-lock.json ...                                                                                                            packages/polyserve/package-lock.json ... +6321/-5429

---

💡 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 a dependency to a newer version for security improvements Update the http-proxy-middleware package to version 0.18.0 to address potential security vulnerabilities in the older version. packages/polyserve/package.json [52] +"http-proxy-middleware": "^0.18.0", - Apply this suggestion Suggestion importance[1-10]: 9 Why: The suggestion correctly identifies the update of the http-proxy-middleware package to version 0.18.0, which addresses potential security vulnerabilities in the older version. This is a crucial update for maintaining security.	9

[qodo-merge-pro]

CI Failure Feedback 🧐

(Checks updated until commit b19b22a)

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: The command npm ci exited with code 1 in the package 'wct-mocha'. There were multiple deprecation warnings for various npm packages, indicating that they are no longer supported. The specific error details are not provided in the log, but the failure of npm ci suggests issues with package installation or compatibility.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 566: npm WARN deprecated [email protected]: This package is no longer supported. 567: npm WARN deprecated [email protected]: This package is no longer supported. 568: npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 569: npm WARN deprecated [email protected]: This package is no longer supported. 570: npm WARN deprecated [email protected]: This package is no longer supported. 571: npm WARN deprecated @lerna/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 572: npm WARN deprecated @lerna/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 573: npm WARN deprecated @lerna/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 574: npm WARN deprecated @lerna/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. ... 748: npm ERR! 749: npm ERR! aliases: clean-install, ic, install-clean, isntall-clean 750: npm ERR! 751: npm ERR! Run "npm help ci" for more info 752: npm ERR! A complete log of this run can be found in: 753: npm ERR! /home/runner/.npm/_logs/2024-09-05T20_44_19_631Z-debug-0.log 754: lerna ERR! npm ci exited 1 in 'wct-mocha' 755: lerna WARN complete Waiting for 1 child process to exit. CTRL-C to exit immediately. 756: ##[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.