build: bump grpcio from 1.65.4 to 1.66.0 in the grpc-deps group#3367
build: bump grpcio from 1.65.4 to 1.66.0 in the grpc-deps group#3367
Conversation
Bumps the grpc-deps group with 1 update: [grpcio](https://github.com/grpc/grpc). Updates `grpcio` from 1.65.4 to 1.66.0 - [Release notes](https://github.com/grpc/grpc/releases) - [Changelog](https://github.com/grpc/grpc/blob/master/doc/grpc_release_schedule.md) - [Commits](grpc/grpc@v1.65.4...v1.66.0) --- updated-dependencies: - dependency-name: grpcio dependency-type: direct:production update-type: version-update:semver-minor dependency-group: grpc-deps ... Signed-off-by: dependabot[bot] <support@github.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3367 +/- ##
==========================================
- Coverage 87.13% 87.12% -0.02%
==========================================
Files 55 55
Lines 9816 9816
==========================================
- Hits 8553 8552 -1
- Misses 1263 1264 +1 |
|
Hello! 👋 Your PR is changing the image cache. So I am attaching the new image cache in a new commit. This commit does not re-run the CICD workflows (since no changes are made in the codebase) therefore you will see the actions showing in their status You might want to rerun the test to make sure that everything is passing. You can retrigger the CICD sending an empty commit You will see this message everytime your commit changes the image cache but you are not attaching the updated cache. 🤓 |
Bumps the grpc-deps group with 1 update: grpcio.
Updates
grpciofrom 1.65.4 to 1.66.0Release notes
Sourced from grpcio's releases.
... (truncated)
Commits
13cecab[Release] Bump version to 1.66.0 (on v1.66.x branch) (#37554)56a8122[Release] Bump version to 1.66.0-pre5 (on v1.66.x branch) (#37517)c0f06b9[OTel C++] Fix race when adding and removing callbacks (#37485) (#37508)e53a314[RlsLB] Fix Deadlock (#37459) (#37502)bee26a7[Release] Bump version to 1.66.0-pre4 (on v1.66.x branch) (#37501)e9c0c1a[secure endpoint] backport fix from #37482 to 1.66.x (#37500)4a15da4[Python Otel] Manage call tracer life cycle use call arena. (v1.66.x backport...87f9724[Python Distrib] Change warning to RuntimeError for version incompatibility (...0ef0d1c[backport] fix memory leak in secure endpoint (#37475)d378d34Add psm-dualstack.cfg for cpp and python (v1.66.x backport) (#37446)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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions