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

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v5.0.0-alpha.17

2025-06-29

This release stabilizes many APIs for the imminent OkHttp 5.0.0 release.

• New: TrailersSource, a public API for HTTP trailers. Production callers shouldn't need this
  as the API to read response trailers is unchanged. Testers may use this new stable API to
  supply trailers for a Response.

• New: Path.asRequestBody() is now a non-experimental API.

• New: FileDescriptor.toRequestBody() is now a non-experimental API.

• New: Stop using experimental coroutines APIs in our okhttp-coroutines artifact.

• Breaking: Move gzip from RequestBody to Request.Builder. This new API handles both
  compressing the request body and also adding the corresponding Content-Encoding header. Note
  that this function is sensitive to when it is called: the response body must be supplied before
  it can be compressed.

• Breaking: Remove AddressPolicy, AsyncDns, and ConnectionListener from the public API. We
  intend to ship a public API for these features, but we don't want to hold OkHttp 5.0.0 until
  those APIs are stable.

• Fix: Change MockWebServer.close() to cancel ongoing calls that are blocked on a delay.

• Upgrade: [Okio 3.13.0][okio_3_13_0].

This release also stabilizes many APIs in the mockwebserver3 artifact that's new in 5.0.

• Breaking: RecordedRequest.body is now nullable. Null is used when the request does not have a
  body.

• Breaking: RecordedRequest.chunkSizes is now nullable. Null is used when the request does not
  use chunked encoding. This is different from an empty list - that indicates the request is
  chunked but has no data.

• Breaking: Replace SocketPolicy with a new type, SocketEffect. It splits triggers (request
  start, response body, etc.) from effects (closing the socket, closing the stream, etc.).

• Breaking: Rename RecordedRequest.sequenceNumber to exchangeIndex and introduce
  connectionIndex on that type. These properties may be useful when testing features like
  connection reuse.

• Breaking: Replace our parameters-based JUnit 5 extension with a new annotation, @StartStop.
  Put this annotation on a MockWebServer property and the extension will start it before your
  test executes and stop it after it completes. No further configuration is required.

  @​StartStop val server = MockWebServer()

• Breaking: Don't automatically start MockWebServer after calls to accessors like port. Now
  these accessors will throw an IllegalStateException if the service has not yet been started.

• Breaking: Decompose the RecordedRequest.requestLine into three properties, method, target,
  and version. This better suits HTTP/2 where the request line had to be synthesized from
  component headers.

• Breaking: Change RecordedRequest.body from a mutable Buffer to an immutable ByteString.

• Breaking: Adopt Okio's new Socket interface for MockResponse.socketHandler.

Note that any Breaking changes above impact only APIs introduced in earlier 5.0.0-alpha releasees.
We don't break binary compatibility with non-alpha APIs.

---

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.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[MartelliEnrico]

LGTM