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 paymentservice #66

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

Conversation

elastic-renovate-prod[bot]
Copy link

@elastic-renovate-prod elastic-renovate-prod bot commented Sep 1, 2024

This PR contains the following updates:

Package Type Update Change
@grpc/grpc-js (source) dependencies minor 1.10.8 -> 1.11.3
@​openfeature/flagd-provider dependencies patch 0.13.0 -> 0.13.1
@openfeature/server-sdk dependencies minor 1.14.0 -> 1.15.1
@opentelemetry/api (source) dependencies minor 1.8.0 -> 1.9.0
grpc-js-health-check dependencies minor 1.1.0 -> 1.2.2
pino (source) dependencies minor 8.16.1 -> 8.21.0

Release Notes

grpc/grpc-node (@​grpc/grpc-js)

v1.11.3: @​grpc/grpc-js 1.11.3

Compare Source

  • Ensure the client queries the name resolver again after connections drop while using the round_robin load balancing policy (#​2825)

v1.11.2: @​grpc/grpc-js 1.11.2

Compare Source

  • Fix client crash on receiving a custom error code (#​2801 contributed by @​hastom)
  • Report connection errors more consistently (#​2808)
  • Avoid computing the channel constructor trace log when that tracer is not enabled (#​2817 contributed by @​ygalbel)

v1.11.1: @​grpc/grpc-js 1.11.1

Compare Source

  • Revert a change that used APIs that were not available in early minor versions of Node 14 (#​2799 contributed by @​xqin)

v1.11.0: @​grpc/grpc-js 1.11.0

Compare Source

Changelog

Experimental API changes

Added:

  • splitHostPort
  • HostPort
  • createServerCredentialsWithInterceptors

v1.10.11: @​grpc/grpc-js 1.10.11

Compare Source

  • Fix a bug that caused clients to reconnect unnecessarily while no requests are pending. (#​2784)
  • Fix a bug that caused clients to fail to re-establish existing connections while waiting for DNS results (#​2784)
  • Fix a bug that caused servers to sometimes not close idle connections depending on timing (#​2790)
  • Fix a bug that caused calls to be pending indefinitely while unable to start after a channel is closed (#​2791)

v1.10.10: @​grpc/grpc-js 1.10.10

Compare Source

  • Various improvements to handling of keepalive timers (#​2760 by @​davidfiala)
  • Fix a bug causing unary response client requests to hang when unexpectedly receiving multiple messages (#​2772)
  • Fix a bug causing some requests to fail when making requests through a local proxy (#​2746 contributed by @​mjameswh, backported in #​2777)
  • Fix handling of URL-encoded user credentials in proxy configuration (#​2761 contributed by @​brendan-myers, backported in #​2777)
  • Fix missing client-side handling of the grpc.max_send_message_length channel option (#​2779)

v1.10.9: @​grpc/grpc-js 1.10.9

Compare Source

  • Avoid buffering significantly more than grpc.max_receive_message_size per received message.
open-feature/js-sdk (@​openfeature/server-sdk)

v1.15.1

Compare Source

v1.15.0

Compare Source

open-telemetry/opentelemetry-js (@​opentelemetry/api)

v1.9.0

Compare Source

🚀 (Enhancement)
  • feat(instrumentation-grpc): set net.peer.name and net.peer.port on client spans #​3430
  • feat(exporter-trace-otlp-proto): Add protobuf otlp trace exporter support for browser #​3208 @​pkanal
🐛 (Bug Fix)
  • fix(sdk-metrics): use default Resource to comply with semantic conventions #​3411 @​pichlermarc
    • Metrics exported by the SDK now contain the following resource attributes by default:
      • service.name
      • telemetry.sdk.name
      • telemetry.sdk.language
      • telemetry.sdk.version
  • fix(sdk-metrics): use Date.now() for instrument recording timestamps #​3514 @​MisterSquishy
  • fix(sdk-trace): make spans resilient to clock drift #​3434 @​dyladan
  • fix(selenium-tests): updated webpack version for selenium test issue #​3456 @​SaumyaBhushan
  • fix(sdk-metrics): collect metrics when periodic exporting metric reader flushes #​3517 @​legendecas
  • fix(sdk-metrics): fix duplicated registration of metrics for collectors #​3488 @​legendecas
  • fix(core): fix precision loss in numberToHrtime #​3480 @​legendecas
🏠 (Internal)
khacminh/grpc-js-healthcheck (grpc-js-health-check)

v1.2.2

Compare Source

v1.2.1

Compare Source

v1.2.0

Compare Source

pinojs/pino (pino)

v8.21.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v8.20.0...v8.21.0

v8.20.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v8.19.0...v8.20.0

v8.19.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v8.18.0...v8.19.0

v8.18.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v8.17.2...v8.18.0

v8.17.2

Compare Source

What's Changed

Full Changelog: pinojs/pino@v8.17.1...v8.17.2

v8.17.1

Compare Source

What's Changed

Full Changelog: pinojs/pino@v8.17.0...v8.17.1

v8.17.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v8.16.2...v8.17.0

v8.16.2

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino@v8.16.1...v8.16.2


Configuration

📅 Schedule: Branch creation - "every weekend" (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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Renovate Bot.

@elastic-renovate-prod
Copy link
Author

elastic-renovate-prod bot commented Sep 1, 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: src/paymentservice/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @grpc/[email protected]
npm error node_modules/@grpc/grpc-js
npm error   @grpc/grpc-js@"1.11.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @grpc/grpc-js@"~1.8.0 || ~1.9.0 || ~1.10.0" from @openfeature/[email protected]
npm error node_modules/@openfeature/flagd-provider
npm error   @openfeature/flagd-provider@"0.13.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 /tmp/renovate/cache/others/npm/_logs/2024-09-20T00_52_43_905Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-20T00_52_43_905Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants