Skip to content

Upgrade tonic and prost #6604

Upgrade tonic and prost

Upgrade tonic and prost #6604

Triggered via push September 23, 2024 15:26
Status Failure
Total duration 9s
Artifacts
Check commit message style
2s
Check commit message style
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Check commit message style
The message 1 is invalid: * The first word of the subject ("Upgrade") must not match the first word of the body. Please make the body more informative by adding more information instead of repeating the subject. For example, start by explaining the problem that this change is intended to solve or what was previously missing (e.g., "Previously, ...."). The original message was: Upgrade `tonic` and `prost` Upgrade `tonic` to version 0.12, as a prerequisite to later on upgrading `hyper`. As of version 1, `hyper` no longer uses tokios `AsyncWriter` and `AsyncReader` traits, instead defining its own versions, see <https://github.com/hyperium/hyper/issues/3110>. As tonic `0.12` is updated to use the `hyper 1.0` ecosystem, it changed some of its trait-bounds to the new `hyper` traits. The `hyper-utils` crate provides the wrapper `TokioIo`, which converts between the two. `prost` had to be upgraded as well, for compatibility.
Check commit message style
The following actions use a deprecated Node.js version and will be forced to run on node20: gsactions/commit-message-checker@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/