-
Notifications
You must be signed in to change notification settings - Fork 50
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
Bump outdated deps #97
Conversation
Cargo.toml
Outdated
anyhow = "1" | ||
|
||
serde = { version = "1", features = ["derive"], optional = true } | ||
serde_json = { version = "1", optional = true } | ||
reqwest = { version = "0.11.24", optional = true, default-features = false, features = ["stream", "rustls-tls"] } | ||
reqwest = { version = "0.12.3", optional = true, default-features = false, features = ["stream", "rustls-tls"] } |
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.
reqwest
0.12.0 has extracted the http2 module in a dedicated feature which is enabled by default.
This diff means that we would not support http2 anymore for our REST calls.
I believe it should be reactivated.
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.
but do we really need it? cargo build --all-features
compiles fine without "http2" and "rustls-tls" features.
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.
While we don't strictly need it, I think its better to enable. The server side of things - which reqwest connects to - supports it as well. So we may as well benefit from it there.
* update deps * add http2 feature to reqwest
Updates the dependencies that have newer versions available.
Was there a reason to keep them pinned to their current version?