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

chore(deps): update dependency http-proxy-middleware to v3 #385

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 8, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
http-proxy-middleware ^2.0.6 -> ^3.0.0 age adoption passing confidence

Release Notes

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

v3.0.3

Compare Source

  • fix(pathFilter): handle errors

v3.0.2

Compare Source

  • refactor(dependency): replace is-plain-obj with is-plain-object (#​1031)
  • chore(package): upgrade to eslint v9 (#​1032)
  • fix(logger-plugin): handle undefined protocol and hostname (#​1036)

v3.0.1

Compare Source

  • fix(type): fix RequestHandler return type (#​980)
  • refactor(errors): improve pathFilter error message (#​987)
  • fix(logger-plugin): fix missing target port (#​989)
  • ci(package): npm package provenance (#​991)
  • fix(logger-plugin): log target port when router option is used (#​1001)
  • refactor: fix circular dependencies (#​1010)
  • fix(fix-request-body): support '+json' content-type suffix (#​1015)

v3.0.0

Compare Source

This release contains some breaking changes.

Please read the V3 discussion https://redirect.github.com/chimurai/http-proxy-middleware/discussions/768
or follow the MIGRATION.md guide.

  • feat(typescript): type improvements (#​882)
  • chore(deps): update micromatch to 4.0.5
  • chore(package): bump devDependencies
  • feat(legacyCreateProxyMiddleware): show migration tips (#​756)
  • feat(legacyCreateProxyMiddleware): adapter with v2 behavior (#​754)
  • docs(proxy events): fix new syntax (#​753)
  • feat(debug): improve troubleshooting (#​752)
  • test(path-rewriter): improve coverage (#​751)
  • feat(ejectPlugins): skip registering default plugins (#​750)
  • refactor: logging [BREAKING CHANGE] (#​749)
  • refactor(handlers): refactor to plugins [BREAKING CHANGE] (#​745)
  • feat(plugins): add support for plugins (#​732)
  • docs: fix v3 documentation
  • fix: server mounting [BREAKING CHANGE] (#​731)
  • test(fixRequestBody): fix broken test
  • refactor: use node http base types [BREAKING CHANGE] (#​730) (special thanks: @​cdaringe & @​devanshj)
  • feat(option): refactor context to pathFilter option [BREAKING CHANGE] (#​722)
  • feat: remove shorthand usage [BREAKING CHANGE] (#​716)

v2.0.7

Compare Source

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


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Apr 8, 2024
@renovate renovate bot assigned Avasam Apr 8, 2024
@renovate renovate bot requested a review from Avasam April 8, 2024 02:05
Copy link
Contributor Author

renovate bot commented Apr 8, 2024

⚠ Artifact update problem

Renovate failed to update artifacts 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: tournament-scheduler/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR!   peer react@">= 16.8" from @culturehq/[email protected]
npm ERR!   node_modules/@culturehq/add-to-calendar
npm ERR!     @culturehq/add-to-calendar@"^1.1.2" from the root project
npm ERR!   18 more (@emotion/react, @emotion/styled, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^0.14.0 || ^15.0.0 || ^16.0.0" from [email protected]
npm ERR! node_modules/react-text-mask
npm ERR!   react-text-mask@"^5.4.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^0.14.0 || ^15.0.0 || ^16.0.0" from [email protected]
npm ERR!   node_modules/react-text-mask
npm ERR!     react-text-mask@"^5.4.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-04-08T02_05_29_411Z-debug-0.log

File name: global-scoreboard/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR!   peer react@">=16.3" from @fortawesome/[email protected]
npm ERR!   node_modules/@fortawesome/react-fontawesome
npm ERR!     @fortawesome/react-fontawesome@"^0.2.0" from the root project
npm ERR!   13 more (@react-aria/ssr, @restart/hooks, @restart/ui, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.3.0" from [email protected]
npm ERR! node_modules/react-bootstrap-table-next
npm ERR!   react-bootstrap-table-next@"^4.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.3.0" from [email protected]
npm ERR!   node_modules/react-bootstrap-table-next
npm ERR!     react-bootstrap-table-next@"^4.0.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-04-08T02_05_38_752Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant