-
Notifications
You must be signed in to change notification settings - Fork 69
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(rust): update prost
to v0.12
#202
Conversation
prost
to v0.12prost
to v0.12
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #202 +/- ##
===========================================
+ Coverage 48.72% 65.36% +16.63%
===========================================
Files 23 7 -16
Lines 9920 3560 -6360
Branches 86 0 -86
===========================================
- Hits 4834 2327 -2507
+ Misses 4725 1233 -3492
+ Partials 361 0 -361
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
@@ -8,6 +8,6 @@ edition = "2018" | |||
|
|||
[dependencies] | |||
bytes = "1.0.1" | |||
prost = "0.11" | |||
prost = "0.12" | |||
prost-build = "0.12" |
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.
For some reason, prost-build
was already on v0.12.
This counts as an API-breaking change for the Rust code, right? What's the policy about crate versioning vs. ICS versioning? If we have a change to the Rust crate that's API-breaking but not different at the protocol level, how is that handled? |
No description provided.