5.0.0

💥 Breaks

• Remove unsupported mesh- URI support. This should have no impact for users. (#2474)

💡 Improvements

• Don't mock ErrorDecoder in ConjureBodySerDeTest (#2459)

4.8.0-rc1

💡 Improvements

• Don't mock ErrorDecoder in ConjureBodySerDeTest (#2459)

4.7.0

🐛 Fixes

• Fix request request path to always include leading slash / (#2452)

4.6.0

💡 Improvements

• ApacheHttpClientBlockingChannel uses URL to build request. (#2437)

4.5.0

💡 Improvements

• Implement support for the Proxy-Upstream-Request-Attempts header (#2430)
• Implement the Client-Can-Retry: true hint header for reverse proxies (#2434)

4.4.0

💡 Improvements

• Migrate squareup javapoet to Palantir javapoet (#2410)
• reuse concurrency limiter state when reloading host channels (#2413)
• Retain endpoint concurrency limits on node refresh (#2418)
• QueuedChannel enforces its assumption around at least one in-flight request (#2422)

4.3.0

💡 Improvements

• Optimize target selection and URI parsing (#2398)

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)