[Snyk] Upgrade com.squareup.okhttp3:okhttp from 5.3.2 to 5.4.0

[shafeeqd959]

Snyk has created this PR to upgrade com.squareup.okhttp3:okhttp from 5.3.2 to 5.4.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.

• The recommended version was released 23 days ago.

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[shafeeqd959]

This minor version upgrade introduces a behavioral change that could affect applications in specific edge cases.

Key Changes:

• Behavioral Change: A fix was introduced to limit the total size of headers in an HTTP/2 response to 256 KiB. [1] While this is a safeguard against non-standard server behavior, it could impact applications that rely on receiving unusually large headers.
• New Feature: Interceptors have been enhanced and can now override settings from OkHttpClient.Builder, such as the cache, connection pool, and DNS. [1] This is an additive feature and should not break existing implementations.
• Dependency Upgrades: The release includes updates to kotlinx.coroutines, GraalVM, and Okio. [1]

Recommendation: Verify application behavior if you connect to servers known to send exceptionally large HTTP/2 response headers. For most users, this upgrade is expected to be safe.

Source: OkHttp Change Log

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	0	25	✅ Passed
🟡 Medium Severity	0	1	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	0	90 / 365 days	✅ Passed
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 0
• Medium without fixes: 1
• Low without fixes: 0

✅ BUILD PASSED - All security checks passed

[github-actions]

Coverage Summary

• 📘 Instruction Coverage: 92%
• 🌿 Branch Coverage: 80%