Changelog
*Sourced from [okhttp's changelog](https://github.com/square/okhttp/blob/master/CHANGELOG.md).*
> ## Version 3.14.2
>
> _2019-05-19_
>
> * Fix: Lock in a route when recovering from an HTTP/2 connection error. We had a bug where two
> calls that failed at the same time could cause OkHttp to crash with a `NoSuchElementException`
> instead of the expected `IOException`.
>
> * Fix: Don't crash with a `NullPointerException` when formatting an error message describing a
> truncated response from an HTTPS proxy.
>
>
> ## Version 4.0.0-ALPHA01
>
> _2019-05-08_
>
> This is an unstable preview of the OkHttp 4 release. It should not be used.
>
>
> ## Version 3.12.3
>
> _2019-05-07_
>
> * Fix: Permit multipart file names to contain non-ASCII characters.
> * Fix: Retain the `Route` when a connection is reused on a redirect or other follow-up. This was
> causing some `Authenticator` calls to see a null route when non-null was expected.
>
>
> ## Version 3.14.1
>
> _2019-04-10_
>
> * Fix: Don't crash when an interceptor retries when there are no more routes. This was an
> edge-case regression introduced with the events cleanup in 3.14.0.
>
> * Fix: Provide actionable advice when the exchange is non-null. Prior to 3.14, OkHttp would
> silently leak connections when an interceptor retries without closing the response body. With
> 3.14 we detect this problem but the exception was not helpful.
>
> ## Version 3.14.0
>
> _2019-03-14_
>
> * **This release deletes the long-deprecated `OkUrlFactory` and `OkApacheClient` APIs.** These
> facades hide OkHttp's implementation behind another client's API. If you still need this please
> copy and paste [ObsoleteUrlFactory.java][obsolete_url_factory] or
> [ObsoleteApacheClient.java][obsolete_apache_client] into your project.
>
> * **OkHttp now supports duplex calls over HTTP/2.** With normal HTTP calls the request must finish
> before the response starts. With duplex, request and response bodies are transmitted
> ... (truncated)
Commits
- [`b8b6ee8`](https://github.com/square/okhttp/commit/b8b6ee831c65208940c741f8e091ff02425566d5) [maven-release-plugin] prepare release parent-3.14.2
- [`d1c4b1e`](https://github.com/square/okhttp/commit/d1c4b1e486ef3fe7b6f691732abe3d09ce88bac7) Merge pull request [#5068](https://github-redirect.dependabot.com/square/okhttp/issues/5068) from square/jwilson.0518.lock_in_route_
- [`5ecec36`](https://github.com/square/okhttp/commit/5ecec36c2e0c01b466daebd925c64e4c4457f34f) Lock in a route in hasRouteToTry() (3.14.x branch)
- [`ebe5c60`](https://github.com/square/okhttp/commit/ebe5c601304414f0794aaf67203baa0b0cd7de9a) Reproduce NoSuchElementException in RouteSelector.next() in a test
- [`3ec8537`](https://github.com/square/okhttp/commit/3ec8537bf5fda689136660704d5529bb383293ab) Merge pull request [#4976](https://github-redirect.dependabot.com/square/okhttp/issues/4976) from yschimke/another_branch_fix
- [`5d8316b`](https://github.com/square/okhttp/commit/5d8316b4d1cd473f4853b89a1d362db8663b21f2) Testing branch fix
- [`baa96c2`](https://github.com/square/okhttp/commit/baa96c23f4a0681e12c6ada131590b1d6689ba82) Fix 3.14 snapshot builds in Travis after release ([#4926](https://github-redirect.dependabot.com/square/okhttp/issues/4926))
- [`b2c85ba`](https://github.com/square/okhttp/commit/b2c85ba3dd00a484c323b8f9335c79b31145fd51) Merge pull request [#4936](https://github-redirect.dependabot.com/square/okhttp/issues/4936) from TangHuaiZhe/dev2
- [`0db2005`](https://github.com/square/okhttp/commit/0db2005de3c2ff245fddf7599fbdd7ce0a9a7b6d) Fix [#4915](https://github-redirect.dependabot.com/square/okhttp/issues/4915) nullPointerException caused by realConnection is null
- [`a4c0599`](https://github.com/square/okhttp/commit/a4c059967d636187b30afda0eab66e639e1cac04) Ignore dependency:resolve failure on 3.14 branch ([#4924](https://github-redirect.dependabot.com/square/okhttp/issues/4924))
- Additional commits viewable in [compare view](https://github.com/square/okhttp/compare/parent-3.8.0...parent-3.14.2)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Bumps okhttp from 3.8.0 to 3.14.2.
Changelog
*Sourced from [okhttp's changelog](https://github.com/square/okhttp/blob/master/CHANGELOG.md).* > ## Version 3.14.2 > > _2019-05-19_ > > * Fix: Lock in a route when recovering from an HTTP/2 connection error. We had a bug where two > calls that failed at the same time could cause OkHttp to crash with a `NoSuchElementException` > instead of the expected `IOException`. > > * Fix: Don't crash with a `NullPointerException` when formatting an error message describing a > truncated response from an HTTPS proxy. > > > ## Version 4.0.0-ALPHA01 > > _2019-05-08_ > > This is an unstable preview of the OkHttp 4 release. It should not be used. > > > ## Version 3.12.3 > > _2019-05-07_ > > * Fix: Permit multipart file names to contain non-ASCII characters. > * Fix: Retain the `Route` when a connection is reused on a redirect or other follow-up. This was > causing some `Authenticator` calls to see a null route when non-null was expected. > > > ## Version 3.14.1 > > _2019-04-10_ > > * Fix: Don't crash when an interceptor retries when there are no more routes. This was an > edge-case regression introduced with the events cleanup in 3.14.0. > > * Fix: Provide actionable advice when the exchange is non-null. Prior to 3.14, OkHttp would > silently leak connections when an interceptor retries without closing the response body. With > 3.14 we detect this problem but the exception was not helpful. > > ## Version 3.14.0 > > _2019-03-14_ > > * **This release deletes the long-deprecated `OkUrlFactory` and `OkApacheClient` APIs.** These > facades hide OkHttp's implementation behind another client's API. If you still need this please > copy and paste [ObsoleteUrlFactory.java][obsolete_url_factory] or > [ObsoleteApacheClient.java][obsolete_apache_client] into your project. > > * **OkHttp now supports duplex calls over HTTP/2.** With normal HTTP calls the request must finish > before the response starts. With duplex, request and response bodies are transmitted > ... (truncated)Commits
- [`b8b6ee8`](https://github.com/square/okhttp/commit/b8b6ee831c65208940c741f8e091ff02425566d5) [maven-release-plugin] prepare release parent-3.14.2 - [`d1c4b1e`](https://github.com/square/okhttp/commit/d1c4b1e486ef3fe7b6f691732abe3d09ce88bac7) Merge pull request [#5068](https://github-redirect.dependabot.com/square/okhttp/issues/5068) from square/jwilson.0518.lock_in_route_ - [`5ecec36`](https://github.com/square/okhttp/commit/5ecec36c2e0c01b466daebd925c64e4c4457f34f) Lock in a route in hasRouteToTry() (3.14.x branch) - [`ebe5c60`](https://github.com/square/okhttp/commit/ebe5c601304414f0794aaf67203baa0b0cd7de9a) Reproduce NoSuchElementException in RouteSelector.next() in a test - [`3ec8537`](https://github.com/square/okhttp/commit/3ec8537bf5fda689136660704d5529bb383293ab) Merge pull request [#4976](https://github-redirect.dependabot.com/square/okhttp/issues/4976) from yschimke/another_branch_fix - [`5d8316b`](https://github.com/square/okhttp/commit/5d8316b4d1cd473f4853b89a1d362db8663b21f2) Testing branch fix - [`baa96c2`](https://github.com/square/okhttp/commit/baa96c23f4a0681e12c6ada131590b1d6689ba82) Fix 3.14 snapshot builds in Travis after release ([#4926](https://github-redirect.dependabot.com/square/okhttp/issues/4926)) - [`b2c85ba`](https://github.com/square/okhttp/commit/b2c85ba3dd00a484c323b8f9335c79b31145fd51) Merge pull request [#4936](https://github-redirect.dependabot.com/square/okhttp/issues/4936) from TangHuaiZhe/dev2 - [`0db2005`](https://github.com/square/okhttp/commit/0db2005de3c2ff245fddf7599fbdd7ce0a9a7b6d) Fix [#4915](https://github-redirect.dependabot.com/square/okhttp/issues/4915) nullPointerException caused by realConnection is null - [`a4c0599`](https://github.com/square/okhttp/commit/a4c059967d636187b30afda0eab66e639e1cac04) Ignore dependency:resolve failure on 3.14 branch ([#4924](https://github-redirect.dependabot.com/square/okhttp/issues/4924)) - Additional commits viewable in [compare view](https://github.com/square/okhttp/compare/parent-3.8.0...parent-3.14.2)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.