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 frontend #162

Closed
wants to merge 1 commit into from

Conversation

mend-for-github-com[bot]
Copy link

This PR contains the following updates:

Package Type Update Change
@grpc/grpc-js (source) dependencies patch 1.9.9 -> 1.9.15
ts-proto dependencies minor 1.163.0 -> 1.164.0

By merging this PR, the below vulnerabilities will be automatically resolved:

Severity CVSS Score CVE
Medium Medium 5.3 CVE-2024-37168

By merging this PR, the issue #141 will be automatically resolved and closed:

Severity CVSS Score CVE
Critical Critical 9.8 CVE-2023-36665

Release Notes

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

v1.9.15: @​grpc/grpc-js 1.9.15

Compare Source

  • Avoid buffering significantly more than grpc.max_receive_message_size per received message.

v1.9.14: @​grpc/grpc-js 1.9.14

Compare Source

  • Fix a bug that could rarely cause connection leaks (#​2644)
  • Fix a bug that could cause clients to go IDLE incorrectly some time after calling waitForReady (#​2643)

v1.9.13: @​grpc/grpc-js 1.9.13

Compare Source

  • Fix a bug that could cause the Node process to close early when establishing a connection while a request is pending (#​2626)

v1.9.12: @​grpc/grpc-js 1.9.12

Compare Source

  • Fix a bug that could cause connectivity state information to become stale in some circumstances (#​2623)

v1.9.11: @​grpc/grpc-js 1.9.11

Compare Source

  • Fix a busy loop when recovering from a failure to establish a connection to a unix domain socket address target (#​2618)
  • Fix a bug that caused clients to stop trying to connect to a fixed IP address target after a working connection drops (#​2619)

v1.9.10: @​grpc/grpc-js 1.9.10

Compare Source

  • Provide the correct port to the proxy when connecting to a target without an explicitly specified port (#​2608 contributed by @​segevfiner)
  • Properly handle goaway events with no additional data attached (#​2611)
stephenh/ts-proto (ts-proto)

v1.164.0

Compare Source

Features
  • add before and after request methods to base service (#​961) (19ba6a5)

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

Copy link

github-actions bot commented Sep 3, 2024

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Sep 3, 2024
Copy link

Closed as inactive. Feel free to reopen if this PR is still being worked on.

@github-actions github-actions bot closed this Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security fix Security fix generated by Mend Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants