Skip to content

fix(deps): update dependency socket.io to v4.8.3#16125

Merged
kamilmysliwiec merged 1 commit into
masterfrom
renovate/socket.io-packages
Dec 26, 2025
Merged

fix(deps): update dependency socket.io to v4.8.3#16125
kamilmysliwiec merged 1 commit into
masterfrom
renovate/socket.io-packages

Conversation

@renovate

@renovate renovate Bot commented Dec 24, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
socket.io (source) 4.8.2 -> 4.8.3 age confidence

Release Notes

socketio/socket.io (socket.io)

v4.8.3

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 commented Dec 24, 2025

Copy link
Copy Markdown
Contributor Author

⚠️ 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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @opentelemetry/core@1.15.2
npm warn Found: @opentelemetry/api@1.9.0
npm warn node_modules/@opentelemetry/api
npm warn   @opentelemetry/api@"^1.0.0" from @opentelemetry/api-logs@0.41.2
npm warn   node_modules/@opentelemetry/api-logs
npm warn     @opentelemetry/api-logs@"0.41.2" from @opentelemetry/otlp-transformer@0.41.2
npm warn     node_modules/@opentelemetry/otlp-transformer
npm warn     1 more (@opentelemetry/sdk-logs)
npm warn   38 more (@opentelemetry/context-async-hooks, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer @opentelemetry/api@">=1.0.0 <1.5.0" from @opentelemetry/core@1.15.2
npm warn node_modules/@opentelemetry/core
npm warn   @opentelemetry/core@"1.15.2" from @opentelemetry/exporter-metrics-otlp-grpc@0.41.2
npm warn   node_modules/@opentelemetry/exporter-metrics-otlp-grpc
npm warn   16 more (@opentelemetry/resources, ...)
npm warn
npm warn Conflicting peer dependency: @opentelemetry/api@1.4.1
npm warn node_modules/@opentelemetry/api
npm warn   peer @opentelemetry/api@">=1.0.0 <1.5.0" from @opentelemetry/core@1.15.2
npm warn   node_modules/@opentelemetry/core
npm warn     @opentelemetry/core@"1.15.2" from @opentelemetry/exporter-metrics-otlp-grpc@0.41.2
npm warn     node_modules/@opentelemetry/exporter-metrics-otlp-grpc
npm warn     16 more (@opentelemetry/resources, ...)
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @opentelemetry/otlp-transformer@0.41.2
npm warn Found: @opentelemetry/api@1.9.0
npm warn node_modules/@opentelemetry/api
npm warn   @opentelemetry/api@"^1.0.0" from @opentelemetry/api-logs@0.41.2
npm warn   node_modules/@opentelemetry/api-logs
npm warn     @opentelemetry/api-logs@"0.41.2" from @opentelemetry/otlp-transformer@0.41.2
npm warn     node_modules/@opentelemetry/otlp-transformer
npm warn     1 more (@opentelemetry/sdk-logs)
npm warn   38 more (@opentelemetry/context-async-hooks, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer @opentelemetry/api@">=1.3.0 <1.5.0" from @opentelemetry/otlp-transformer@0.41.2
npm warn node_modules/@opentelemetry/otlp-transformer
npm warn   @opentelemetry/otlp-transformer@"0.41.2" from @opentelemetry/exporter-metrics-otlp-grpc@0.41.2
npm warn   node_modules/@opentelemetry/exporter-metrics-otlp-grpc
npm warn   2 more (@opentelemetry/exporter-metrics-otlp-http, @opentelemetry/exporter-trace-otlp-http)
npm warn
npm warn Conflicting peer dependency: @opentelemetry/api@1.4.1
npm warn node_modules/@opentelemetry/api
npm warn   peer @opentelemetry/api@">=1.3.0 <1.5.0" from @opentelemetry/otlp-transformer@0.41.2
npm warn   node_modules/@opentelemetry/otlp-transformer
npm warn     @opentelemetry/otlp-transformer@"0.41.2" from @opentelemetry/exporter-metrics-otlp-grpc@0.41.2
npm warn     node_modules/@opentelemetry/exporter-metrics-otlp-grpc
npm warn     2 more (@opentelemetry/exporter-metrics-otlp-http, @opentelemetry/exporter-trace-otlp-http)
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @opentelemetry/sdk-logs@0.41.2
npm warn Found: @opentelemetry/api@1.9.0
npm warn node_modules/@opentelemetry/api
npm warn   @opentelemetry/api@"^1.0.0" from @opentelemetry/api-logs@0.41.2
npm warn   node_modules/@opentelemetry/api-logs
npm warn     @opentelemetry/api-logs@"0.41.2" from @opentelemetry/otlp-transformer@0.41.2
npm warn     node_modules/@opentelemetry/otlp-transformer
npm warn     1 more (@opentelemetry/sdk-logs)
npm warn   38 more (@opentelemetry/context-async-hooks, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer @opentelemetry/api@">=1.4.0 <1.5.0" from @opentelemetry/sdk-logs@0.41.2
npm warn node_modules/@opentelemetry/sdk-logs
npm warn   @opentelemetry/sdk-logs@"0.41.2" from @opentelemetry/otlp-transformer@0.41.2
npm warn   node_modules/@opentelemetry/otlp-transformer
npm warn
npm warn Conflicting peer dependency: @opentelemetry/api@1.4.1
npm warn node_modules/@opentelemetry/api
npm warn   peer @opentelemetry/api@">=1.4.0 <1.5.0" from @opentelemetry/sdk-logs@0.41.2
npm warn   node_modules/@opentelemetry/sdk-logs
npm warn     @opentelemetry/sdk-logs@"0.41.2" from @opentelemetry/otlp-transformer@0.41.2
npm warn     node_modules/@opentelemetry/otlp-transformer
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: sinon-chai@4.0.1
npm error Found: chai@4.5.0
npm error node_modules/chai
npm error   dev chai@"4.5.0" from the root project
npm error   peer chai@">= 2.1.2 < 6" from chai-as-promised@7.1.2
npm error   node_modules/chai-as-promised
npm error     dev chai-as-promised@"7.1.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer chai@"^5.0.0 || ^6.0.0" from sinon-chai@4.0.1
npm error node_modules/sinon-chai
npm error   dev sinon-chai@"4.0.1" from the root project
npm error
npm error Conflicting peer dependency: chai@6.2.2
npm error node_modules/chai
npm error   peer chai@"^5.0.0 || ^6.0.0" from sinon-chai@4.0.1
npm error   node_modules/sinon-chai
npm error     dev sinon-chai@"4.0.1" 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 /runner/cache/others/npm/_logs/2025-12-26T12_39_29_284Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-26T12_39_29_284Z-debug-0.log

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Dec 24, 2025
@coveralls

Copy link
Copy Markdown

Pull Request Test Coverage Report for Build c48f1193-4f78-4ee3-9001-8e03668bce02

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 89.709%

Totals Coverage Status
Change from base Build 0163207d-c675-4aa1-8a99-331fb402390f: 0.0%
Covered Lines: 7436
Relevant Lines: 8289

💛 - Coveralls

@kamilmysliwiec kamilmysliwiec merged commit beb852a into master Dec 26, 2025
4 of 5 checks passed
@renovate renovate Bot changed the title fix(deps): update socket.io packages to v4.8.3 fix(deps): update dependency socket.io to v4.8.3 Dec 26, 2025
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.

2 participants