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

fix(deps): update dependency http-proxy-middleware to v2 [security] #573

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
http-proxy-middleware 0.21.0 -> 2.0.7 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2024-21536

Versions of the package http-proxy-middleware before 2.0.7, from 3.0.0 and before 3.0.3 are vulnerable to Denial of Service (DoS) due to an UnhandledPromiseRejection error thrown by micromatch. An attacker could kill the Node.js process and crash the server by making requests to certain paths.


Release Notes

chimurai/http-proxy-middleware (http-proxy-middleware)

v2.0.7

Compare Source

Full Changelog: chimurai/http-proxy-middleware@v2.0.6...v2.0.7

v2.0.6

Compare Source

  • fix(proxyReqWs): catch socket errors (#​763)

v2.0.5

Compare Source

  • fix(error handler): add default handler to econnreset (#​759)

v2.0.4

Compare Source

  • fix(fix-request-body): improve content type check (#​725) (kevinxh)

v2.0.3

Compare Source

v2.0.2

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source

  • chore(package): drop node 10 [BREAKING CHANGE] (#​577)

v1.3.1

Compare Source

  • fix(fix-request-body): make sure the content-type exists (#​578) (oufeng)

v1.3.0

Compare Source

  • docs(response interceptor): align with nodejs default utf8 (#​567)
  • feat: try to proxy body even after body-parser middleware (#​492) (midgleyc)

v1.2.1

Compare Source

  • fix(response interceptor): proxy original response headers (#​563)

v1.2.0

Compare Source

  • feat(handler): response interceptor (#​520)
  • fix(log error): handle undefined target when websocket errors (#​527)

v1.1.2

Compare Source

  • fix(log error): handle optional target (#​523)

v1.1.1

Compare Source

  • fix(error handler): re-throw http-proxy missing target error (#​517)
  • refactor(dependency): remove camelcase
  • fix(option): optional target when router is used (#​512)

v1.1.0

Compare Source

v1.0.6

Compare Source

  • chore(deps): lodash 4.17.20 (#​475)

v1.0.5

Compare Source

  • chore(deps): lodash 4.17.19 (#​454)

v1.0.4

Compare Source

  • chore(deps): http-proxy 1.18.1 (#​442)

v1.0.3

Compare Source

  • build(package): exclude build artifact tsconfig.tsbuildinfo (#​415)

v1.0.2

Compare Source

  • fix(router): handle rejected promise in custom router (#​410) (bforbis)

v1.0.1

Compare Source

  • fix(typescript): fix proxyRes and router types (#​410) (dylang)

v1.0.0

Compare Source

  • feat(createProxyMiddleware): explicit import http-proxy-middleware (BREAKING CHANGE)(#​400)
  • feat(typescript): export http-proxy-middleware types (#​400)
  • fix(typescript): ES6 target - TS1192 (#​400)

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Oct 25, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: webui/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @material-ui/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"18.3.1" from the root project
npm ERR!   peer react@"^18.3.1" from [email protected]
npm ERR!   node_modules/react-dom
npm ERR!     react-dom@"18.3.1" from the root project
npm ERR!   1 more (react-scripts)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0" from @material-ui/[email protected]
npm ERR! node_modules/@material-ui/core
npm ERR!   dev @material-ui/core@"4.12.4" from the root project
npm ERR!   peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm ERR!   node_modules/@material-ui/icons
npm ERR!     dev @material-ui/icons@"4.11.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0 || ^17.0.0" from @material-ui/[email protected]
npm ERR!   node_modules/@material-ui/core
npm ERR!     dev @material-ui/core@"4.12.4" from the root project
npm ERR!     peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm ERR!     node_modules/@material-ui/icons
npm ERR!       dev @material-ui/icons@"4.11.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-10-25T03_47_06_960Z-debug-0.log

@renovate renovate bot requested a review from adamdecaf as a code owner October 25, 2024 03:47
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.

0 participants