-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Update protobuf, skylib, rules_go, grpc-gateway dependencies #5657
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5657 +/- ##
===========================================
+ Coverage 15.44% 56.06% +40.62%
===========================================
Files 116 312 +196
Lines 9403 25870 +16467
===========================================
+ Hits 1452 14504 +13052
- Misses 7722 9311 +1589
- Partials 229 2055 +1826 |
WORKSPACE
Outdated
urls = [ | ||
"https://mirror.bazel.build/github.com/bazelbuild/rules_go/releases/download/v0.22.2/rules_go-v0.22.2.tar.gz", | ||
"https://github.com/bazelbuild/rules_go/releases/download/v0.22.2/rules_go-v0.22.2.tar.gz", | ||
"https://mirror.bazel.build/github.com/bazelbuild/rules_go/releases/download/v0.21.7/rules_go-v0.21.7.tar.gz", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did you decide to downgrade io_bazel_rules_go . i think it was upgraded to support go 1.14
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh no! I didn’t mean to downgrade. Nice catch, i’ll Fix tomorrow
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
What type of PR is this?
Other
What does this PR do? Why is it needed?
Updates protobuf, skylib, rules_go, grpc-gateway.
Which issues(s) does this PR fix?
Part of #5651
Other notes for review
This PR allows for the requests outlined in #5651 to work if the parameters are properly URL encoded. I'm not marking that issue as "fixed" because this is different behavior from our envoy production implementation of https://api.prylabs.net