GitoxideLabs/gitoxide git-transport-v0.21.0

git-transport v0.21.0

on GitHub

New Features

• reqwest as blocking HTTP backend via http-client-reqwest feature toggle.
  Note that despite passing the same tests that curl passes, for
  bulletproof HTTP connections to untrusted servers, the curl backend
  should be preferred. reqwest is known to hang if content-length:
  HTTP headers are longer than the actual content, and no timeout is
  kicking in to stop the hanging. curl has no trouble with this for
  example.
• Add client::http::Transport::new_http() constructor.
  This goes along with client::http::connect_http() to support
  connections to via custom transports which are passed from calling
  crates, without relying on the implementation to be built-in.
• Allow defaulting client::Capabilities.
  This can be useful in conjunction with std::mem::take(), even
  though an empty data structure like that doesn't bear any significance
  beyond that.

Bug Fixes

• set the protocol version for local git transports as well.
  Previously this was only done for ssh based connections, and requires
  setting an environment variable.

• remove Drop for SpawnProcessOnDemand.
  It is well-intended but is likely to hang the calling process
  if for any reason not all process output was consumed.

  Even though not waiting for the process leaves it running, it will
  stop naturally once its output pipe breaks once once
  our handles for it are inevitable dropped at the same time.

• compare 'Content-Type' header case-insensitively, as required by the http spec.

Other

• try to make the transport configurable after being boxed, but…
  …that would force it to be 'static, which is something we excplicitly
  cannot have. We need references to be contained within, if I remember
  correctly.

Changed (BREAKING)

• client::http::connect() returns Transport<Impl> directly.
  It' can't fail, so no need to return Result<_, Infallible>.

New Features (BREAKING)

• add fetch::Transport::configure to generically configure any transport.

Commit Statistics

• 42 commits contributed to the release over the course of 20 calendar days.
• 20 days passed between releases.
• 9 commits were understood as conventional.
• 1 unique issue was worked on: #450

Commit Details