ds-cbo/forgejo-api:bump-dependencies into main Ran cargo upgrade --incompatible and cargo update to bump dependencies, then cargo test to check what broke
@ -11,3 +11,3 @@
[dependencies]
reqwest = { version = "0.12", default-features = false, features = ["charset", "http2", "macos-system-configuration", "json", "multipart"] }
reqwest = { version = "0.13.4", default-features = false, features = ["charset", "http2", "system-proxy", "json", "multipart"] }
macos-system-configuration was renamed to system-proxy, see https://github.com/seanmonstar/reqwest/pull/2901
@ -29,2 +29,3 @@
sync = ["reqwest/blocking"]
rustls-tls = ["reqwest/rustls-tls"]
rustls-tls = ["reqwest/rustls"]
native-tls = ["reqwest/native-tls"]
rustls-tls feature was renamed to rustls, added native-tls feature
should we rename forgejo-api feature to just rustls as well? would be a breaking change, but would align with upstream
I think it's fine to leave it as-is.
@ -34,2 +34,2 @@
reqwest = { version = "0.12", features = ["cookies"] }
tokio = { version = "1.29.1", features = ["net", "fs", "rt", "macros"] }
eyre = "0.6.12"
reqwest = { version = "0.13", features = ["cookies", "form"] }
tests use RequestBuilder::form(), was extracted to reqwest feature form
Thanks!
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?