Update dependency com.squareup.okhttp3:mockwebserver3-junit5 to v5.0.0-alpha.16

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.squareup.okhttp3:mockwebserver3-junit5 (source)	5.0.0-alpha.14 -> 5.0.0-alpha.16

---

Release Notes

square/okhttp (com.squareup.okhttp3:mockwebserver3-junit5)

v5.0.0-alpha.16

2024-05-29

• Fix: The previous release would crash when running on Robolectric. We didn't anticipate
  running our Android artifact on the JVM platform!

v5.0.0-alpha.15

2024-05-28

This release introduces separate JVM and Android artifacts. Until now, we've distributed OkHttp
as a JVM library that detects Android capabilities at runtime, but that doesn't offer
Android-specific APIs. With this release we're starting to publish OkHttp as an AAR for Android
users in addition to our existing JAR for JVM users.

This first Android-specific artifact adopts Android's assets mechanism to embed the public suffix
data. We will build more Android integration in future releases.

The okhttp-android artifact first introduced in 5.0.0-alpha.7 is no longer available:

• The AndroidAsyncDns class moved to the okhttp artifact.
• The AndroidLogging class is no longer necessary. LoggingEventListener and
  HttpLoggingInterceptor write to logcat by default.

The rest of this release is our highest-quality release yet. Though we continue to use the word
alpha in the version name, the only unstable thing in it is some non-final APIs tagged
@ExperimentalOkHttpApi. You can safely use this release in production.

• Fix: Attempt to read the response even if sending the request failed. This makes it possible
  to handle response statuses like HTTP/1.1 431 "Request Header Fields Too Large.

• Fix: Handle multiple 1xx responses.

• Fix: Address a performance bug in our internal task runner. We had a race condition that could
  result in it OkHttp starting a thread for each queued task, even when a single thread could run
  all of them.

• Fix: Address a performance bug in MultipartReader. We were scanning the entire input stream
  for a delimiter when we only needed to scan enough to return a result.

• Fix: Don't double-compress the public suffix database. OkHttp is usually distributed in a
  compressed file (like a JAR or APK), so compressing its internal data was redundant.

• Fix: Call ProxySelector.connectFailed() when a connection's initial TCP handshake fails.

• Fix: Change the signature of Dispatcher to accept a nullable ExecutorService. Changing this
  parameter to be non-null was an unintended signature change in OkHttp 4.0.

• New: EventListener.retryDecision() is called each time a request fails with an IOException.
  It notifies your listener if OkHttp will retry.

• New: EventListener.followUpDecision() is called each time a response is received. It notifies
  your listener if OkHttp has decided to make a follow-up request. Some common follow-ups are
  authentication challenges and redirects.

• New: Handy constants for Headers.EMPTY, RequestBody.EMPTY, and ResponseBody.EMPTY.

• New: OkHttp now calls StrictMode.noteSlowCall() when initializing TLS on Android. Use
  StrictMode to detect if your OkHttpClient is being initialized on the main thread.

• Upgrade: [Okio 3.12.0][okio_3_12_0].

• Upgrade: [Kotlin 2.1.21][kotlin_2_1_21].

• Upgrade: [kotlinx.coroutines 1.10.2][coroutines_1_10_2]. This is used by the optional
  okhttp-coroutines artifact.

• Upgrade: [AndroidX Startup 1.2.0][startup_1_2_0]. The Android variant of the okhttp artifact
  now depends on this. This is a new dependency.

• Upgrade: [AndroidX Annotation 1.9.1][annotation_1_9_1]. As above, the Android variant of the
  okhttp artifact now depends on this. This is also a new dependency.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.