bump grpc to 1.65.0 wrt OCPBUGS-38376 #3892
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yjst2012
force-pushed
the
yjst2012/ARO-11060
branch
4 times, most recently
from
a128ce4
to
689b3b7
Compare
yjst2012
force-pushed
the
yjst2012/ARO-11060
branch
from
689b3b7
to
349cfc0
Compare
|
/azp run ci, e2e |
|
No pipelines are associated with this pull request. |
|
/azp run ci |
|
No pipelines are associated with this pull request. |
yjst2012
added
ready-for-review
skippy
github-actions
bot
added
needs-rebase
|
Please rebase pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue this PR addresses:
fixes https://issues.redhat.com/browse/ARO-11060
What this PR does / why we need it:
the fix for OCPBUGS-38376 is to upgrade google.golang.org/grpc to v1.65.0, and ARO_RP is still on a lower version of grpc, so bump it too
Test plan for issue:
existing unit and e2e tests
Is there any documentation that needs to be updated for this PR?
NA
How do you know this will function as expected in production?
existing unit and e2e tests