chore(deps): bump com.squareup.okio:okio from 3.4.0 to 3.17.0 [Snyk]

[dpatchigolla]

Snyk has created this PR to upgrade com.squareup.okio:okio from 3.4.0 to 3.17.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 20 versions ahead of your current version.

• The recommended version was released 2 months 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

[dpatchigolla]

This upgrade of Okio from version 3.4.0 to 3.17.0 includes several updates, with the most significant being a binary-incompatible change within the okio-fakefilesystem testing module.

Breaking Change:

• okio-fakefilesystem: Version 3.15.0 introduced a breaking change by converting FakeFileSystem.clock from a public field to a property to fix a bug with Gradle 8.x plugins. This change is not binary-compatible and will require projects using FakeFileSystem to be recompiled. Code using this property may need to be updated.

Other Notable Changes:

• The core I/O APIs (Buffer, ByteString, Source, Sink) do not have documented breaking changes in this version range.
• The upgrade path includes numerous features, bug fixes, and dependency updates, including adjustments to the required Kotlin standard library version.

Recommendation:

• If you are using the okio-fakefilesystem artifact for testing, you must recompile your project against the new version and verify any code that accesses FakeFileSystem.clock.
• If you are only using the core okio artifact, the upgrade risk is low, but thorough testing is still recommended.

Source: Okio Changelog

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