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 socket.io packages to v4.8.1 #507

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 30, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
socket.io (source) 4.8.0 -> 4.8.1 age adoption passing confidence
socket.io-client (source) 4.8.0 -> 4.8.1 age adoption passing confidence

Release Notes

socketio/socket.io (socket.io)

v4.8.1

Compare Source

Bug Fixes
  • bundle: do not mangle the "_placeholder" attribute (ca9e994)
Dependencies

Configuration

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

🚦 Automerge: Disabled because a matching PR was automerged previously.

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

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 30, 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: server/package-lock.json
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: [email protected]
npm warn Found: [email protected]
npm warn node_modules/immutable
npm warn   immutable@"5.0.3" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer immutable@"^3.0.0" from [email protected]
npm warn node_modules/chai-immutable
npm warn   dev chai-immutable@"2.1.0" from the root project
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/chai
npm error   dev chai@"5.1.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer chai@"^4.0.0" from [email protected]
npm error node_modules/chai-immutable
npm error   dev chai-immutable@"2.1.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/chai
npm error   peer chai@"^4.0.0" from [email protected]
npm error   node_modules/chai-immutable
npm error     dev chai-immutable@"2.1.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-02T12_40_40_504Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-02T12_40_40_504Z-debug-0.log

File name: client/package-lock.json
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: [email protected]
npm warn Found: [email protected]
npm warn node_modules/immutable
npm warn   immutable@"5.0.3" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer immutable@"^3.0.0" from [email protected]
npm warn node_modules/chai-immutable
npm warn   dev chai-immutable@"2.1.0" from the root project
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/chai
npm error   dev chai@"5.1.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer chai@"^4.0.0" from [email protected]
npm error node_modules/chai-immutable
npm error   dev chai-immutable@"2.1.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/chai
npm error   peer chai@"^4.0.0" from [email protected]
npm error   node_modules/chai-immutable
npm error     dev chai-immutable@"2.1.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-02T12_40_44_168Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-02T12_40_44_168Z-debug-0.log

@renovate renovate bot force-pushed the renovate/socket.io-packages branch from 4b797ff to 7933d4e Compare November 13, 2024 10:33
@renovate renovate bot force-pushed the renovate/socket.io-packages branch from 7933d4e to e0d8eee Compare December 2, 2024 12:40
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