[dcalhoun]

What?

Bump okhttp to 5.5.1.

Why?

Keep okhttp updated with the latest fixes and align with WordPress-Android.

How?

Bump okhttp, and bump compileSdk to 37 as required by the okhttp bump.

Testing Instructions

N/A, no user-facing changes.

Accessibility Testing Instructions

N/A, no user-facing changes.

Screenshots or screencast

N/A, no user-facing changes.

---

AI-generated details

Bumps okhttp 5.3.2 → 5.5.1 and compileSdk 36 → 37, matching WordPress-Android after wordpress-mobile/WordPress-Android#23447.

• OkHttp 5.5.1 blocks the 8 compromised eMudhra intermediate certificates on devices without Google Play Services.
• WordPress-Android already resolves 5.5.1 at runtime, so this aligns the version GBK compiles and tests against with the one that ships.
• okhttp-android 5.4.0+ requires compileSdk 37, which is what failed build(deps): Bump okhttp from 4.12.0 to 5.5.0 in /android #658. WordPress-Android already uses 37.
• The published AAR now declares minCompileSdk=37, so docs/integration.md is updated to match.

Verified locally: make test-android-library-unit, make lint-android, and :app:compileDebugKotlin / checkAarMetadata pass.

🤖 Generated with Claude Code

[wpmobilebot]

XCFramework Build

This PR's XCFramework is available for testing. Add the following to your Package.swift:

.package(url: "https://github.com/wordpress-mobile/GutenbergKit", branch: "pr-build/835")

_{Built from 8b1bbe3}

[nbradbury]

@dcalhoun Claude found one "must fix":

Severity	Merge	Location	Issue	Impact
Medium	Must fix	libs.versions.toml:25	The commit is typed build(android): without the ! breaking-change marker, even though raising the consumer compileSdk floor to 37 is breaking, and #678 used build(android)!: for the bump to 36.	The okhttp-android 5.5.1 AAR declares minCompileSdk=37, so any host app on compileSdk 36 now fails checkAarMetadata, and without ! the release gets no [Type] Breaking Change label to warn integrators other than WordPress-Android.
Low	Could fix	libs.versions.toml:25	Commit 8b1bbe3 ends with a Co-Authored-By: Claude Opus 5.5 trailer, which your global CLAUDE.md forbids.	When the PR is merged, the trailer goes into trunk history unless you amend it out or drop it from the squash message (bumped up from Can wait because it breaks an explicit rule of yours).

[dcalhoun]

@nbradbury I believe the first "must fix" note is not relevant because (A) the PR title including the ! prefix will become the commit when the squash and merge occurs and (B) the PR has a [Type] Breaking Change label—both ensure the release receives a "breaking change" line. The second note appears to be guidance from your own personal agent configuration. WDYT?

[nbradbury]

Looks good