[ANN] httpx 0.19.4 released

httpx 0.19.4 has been released.

HTTPX.get("https://gitlab.com/honeyryderchuck/httpx
<https://gitlab.com/honeyryderchuck/httpx>")

HTTPX is an HTTP client library for the Ruby programming language.

Among its features, it supports:

* HTTP/2 and HTTP/1.x protocol versions
* Concurrent requests by default
* Simple and chainable API
* Proxy Support (HTTP(S), Socks4/4a/5)
* Simple Timeout System
* Lightweight by default (require what you need)

And also:

* Compression (gzip, deflate, brotli)
* Streaming Requests
* Authentication (Basic Auth, Digest Auth, AWS Sigv4)
* Expect 100-continue
* Multipart Requests
* Cookies
* HTTP/2 Server Push
* H2C Upgrade
* Automatic follow redirects
* International Domain Names
* GRPC

# 0.19.4

## Improvements

### Jruby: HTTP/2 with jruby-openssl (>= 0.12.2)

The (optional) FFI-based TLS module for jruby was deleted. Besides it being
cumbersome and hard to maintain, `jruby`'s own `openssl` released support
for ALPN negotiation (in v0.12.2), which solves the problem the deleted
module was supposed to address.

## Bugfixes

* `webmock` integration was fixed to take the mocked URI query string into
account.
* fix internal codepath where mergeable-but-not-coalescable connections
were still triggering the coalesce branch.
* fixed after-use mutation of connection addresses array which was making
it empty after initial usage.
* fixed a "busy loop" caused by long-running native resolver not signaling
it had "nothing to do".

# 0.19.3

## Bugfixes

* `retries` plugin: allow passing floats to `:retry_after` option.
* dns: fixing cache lookups filtering by IP family which was causing socket
connect handshake to start with no IP.

# 0.19.2

## Bugfixes

* skip resolution delay path for early resolve cases

when the early resolve path (using IP, /etc/hosts IP, IP from cache) is
followed, emit_addresses is called, and in a particular case (dual-stack
network but using an IPv4 address), the happy eyeballs resolution delay
path was activated when it shouldn't (it's meant to be used only for DNS
network requests), and resulted in @pool being called before it was ever
set. This simple check ensures that it doesn't happen before it must.

# 0.19.1

## Bugfixes

Fixing a DNS dual-stack case where one the resolvers may have finished way
before the previous one and will therefore return no timeout.