chore(deps): bump google.golang.org/grpc from 1.57.0 to 1.57.1 #427
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.57.0 to 1.57.1. - [Release notes](https://github.com/grpc/grpc-go/releases) - [Commits](grpc/grpc-go@v1.57.0...v1.57.1) --- updated-dependencies: - dependency-name: google.golang.org/grpc dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #427 +/- ##
==========================================
- Coverage 60.11% 60.06% -0.06%
==========================================
Files 99 99
Lines 20045 20033 -12
==========================================
- Hits 12051 12032 -19
- Misses 7691 7699 +8
+ Partials 303 302 -1
☔ View full report in Codecov by Sentry. |
|
I see this in the E2E log: I don't know that I've seen that exact flake before but I'm not prepared to merge this even though this is merely a patch release of a dependency. GRPC ddos prevention could result in scenarios like "text file busy" happening more often. I'm curious how other providers, maintained by Hashicorp, are proceeding. I could imagine an upstream improvement to how the grpc sockets are managed. |
|
Google provider went ahead to 1.58.3 |
|
https://github.com/grpc/grpc-go/releases |
|
Looks like google.golang.org/grpc is up-to-date now, so this is no longer needed. |
dependabot
bot
deleted the
dependabot/go_modules/google.golang.org/grpc-1.57.1
branch
Bumps google.golang.org/grpc from 1.57.0 to 1.57.1.
Release notes
Sourced from google.golang.org/grpc's releases.
Commits
d9c4eabChange version to 1.57.1 (#6712)6a1400dserver: prohibit more than MaxConcurrentStreams handlers from running at once...7511ddfChange version to 1.57.1-dev (#6449)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.