4.2.0

💡 Improvements

• Handle new QoS Metadata (#2375)

4.1.0

✨ Features

• Dialogue produces timer metrics for all endpoints. (#2367)

4.0.0

💥 Breaks

• Dialogue more closely follows the URI specification as defined in rfc3986 section 3.3, and allows colons in http paths and query parameters.

  Note that this is not an API break, however we're using a breaking changelog entry for visibility in case of unknown non-compliant servers.

  Previously the : character would be encoded as %3A, which is also allowed by rfc3986, however not required. Some server implementations, GCP APIs in particular, require colons in path strings not to be encoded.
  This encoding is an implementation detail within dialogue, where either way is valid for servers which are compliant with the rfc.

  It is possible, though unlikely, that some custom servers or proxies do not handle unencoded colons correctly. Please reach out to us if you find cases where servers do not behave as expected! (#2360)

3.137.0

Type	Description	Link
Improvement	Remove client request size metric channel to reduce dialogue metric load	#2300

3.136.0

Type	Description	Link
Improvement	CachingFallbackDnsResolver logs at debug level	#2283

3.135.0

Automated release, no documented user facing changes

3.134.0

Type	Description	Link
Feature	Add support for routing through HTTPS proxies in the apache client when configured	#2279

3.133.0

Type	Description	Link
Improvement	DefaultDialogueDnsResolver logs UnknownHostException at debug	#2277

3.132.0

Type	Description	Link
Improvement	RetryOtherValidatingChannel handles mesh URIs without logging warnings	#2276

3.131.0

Type	Description	Link
Improvement	Avoid expensive refreshable creation in a potentially hot path	#2274