chore: bump the gradle-dependencies group across 1 directory with 39 updates

[dependabot]

Bumps the gradle-dependencies group with 39 updates in the /android directory:

Package	From	To
gradle-wrapper	8.9	9.4.0
androidx.core:core-ktx	1.15.0	1.18.0
androidx.lifecycle:lifecycle-runtime-ktx	2.8.7	2.10.0
androidx.lifecycle:lifecycle-viewmodel-compose	2.8.7	2.10.0
androidx.lifecycle:lifecycle-runtime-compose	2.8.7	2.10.0
androidx.lifecycle:lifecycle-process	2.8.7	2.10.0
androidx.activity:activity-compose	1.9.3	1.13.0
androidx.compose:compose-bom	2024.11.00	2026.03.00
androidx.navigation:navigation-compose	2.8.4	2.9.7
androidx.browser:browser	1.8.0	1.9.0
com.google.dagger:hilt-android	2.52	2.59.2
com.google.dagger:hilt-compiler	2.52	2.59.2
com.google.dagger:hilt-android-testing	2.52	2.59.2
com.google.dagger.hilt.android	2.52	2.59.2
androidx.hilt:hilt-navigation-compose	1.2.0	1.3.0
com.squareup.retrofit2:retrofit	2.11.0	3.0.0
com.squareup.retrofit2:converter-gson	2.11.0	3.0.0
com.squareup.okhttp3:okhttp	4.12.0	5.3.2
com.squareup.okhttp3:logging-interceptor	4.12.0	5.3.2
androidx.datastore:datastore-preferences	1.1.1	1.2.1
androidx.room:room-runtime	2.6.1	2.8.4
androidx.room:room-ktx	2.6.1	2.8.4
androidx.room:room-compiler	2.6.1	2.8.4
io.livekit:livekit-android	2.23.1	2.23.5
androidx.core:core-splashscreen	1.0.1	1.2.0
com.github.SmartToolFactory:Compose-Colorful-Sliders	1.2.2	1.3.0
me.saket.telephoto:zoomable-image-coil	0.14.0	0.18.0
androidx.media3:media3-exoplayer	1.5.0	1.9.2
androidx.media3:media3-ui	1.5.0	1.9.2
androidx.test.ext:junit	1.2.1	1.3.0
androidx.test.espresso:espresso-core	3.6.1	3.7.0
org.jetbrains.kotlinx:kotlinx-coroutines-test	1.9.0	1.10.2
io.mockk:mockk	1.13.13	1.14.9
io.mockk:mockk-android	1.13.13	1.14.9
app.cash.turbine:turbine	1.2.0	1.2.1
com.android.application	8.7.2	9.1.0
org.jetbrains.kotlin.android	2.0.21	2.3.10
org.jetbrains.kotlin.plugin.compose	2.0.21	2.3.10
com.google.devtools.ksp	2.0.21-1.0.27	2.3.6

Updates gradle-wrapper from 8.9 to 9.4.0

Updates androidx.core:core-ktx from 1.15.0 to 1.18.0

Updates androidx.lifecycle:lifecycle-runtime-ktx from 2.8.7 to 2.10.0

Updates androidx.lifecycle:lifecycle-viewmodel-compose from 2.8.7 to 2.10.0

Updates androidx.lifecycle:lifecycle-runtime-compose from 2.8.7 to 2.10.0

Updates androidx.lifecycle:lifecycle-process from 2.8.7 to 2.10.0

Updates androidx.lifecycle:lifecycle-viewmodel-compose from 2.8.7 to 2.10.0

Updates androidx.lifecycle:lifecycle-runtime-compose from 2.8.7 to 2.10.0

Updates androidx.lifecycle:lifecycle-process from 2.8.7 to 2.10.0

Updates androidx.activity:activity-compose from 1.9.3 to 1.13.0

Updates androidx.compose:compose-bom from 2024.11.00 to 2026.03.00

Updates androidx.navigation:navigation-compose from 2.8.4 to 2.9.7

Updates androidx.browser:browser from 1.8.0 to 1.9.0

Updates com.google.dagger:hilt-android from 2.52 to 2.59.2

Release notes

Sourced from com.google.dagger:hilt-android's releases.

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

Dagger 2.59.1

Bug fixes:

• Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
• Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Dagger 2.57.2

Bug fixes

• Fixed #4847: Fixed an issue with the Hilt Gradle Plugin registered transforms on projects using Gradle 9.0.0 (ea570e7)
• Fixes #4898: Fixed an issue with backwards compatibility handling for libraries that export Hilt roots. (85c470ca4)
• Fixes #4937: Fixed the incorrectly declared version of the Kotlin stdlib dependency in the Hilt Gradle Plugin. (deefd9a2d)
• Updated ASM dependency to 9.8 (365bc499d)

... (truncated)

Commits

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-compiler from 2.52 to 2.59.2

Release notes

Sourced from com.google.dagger:hilt-compiler's releases.

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

Dagger 2.59.1

Bug fixes:

• Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
• Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Dagger 2.57.2

Bug fixes

• Fixed #4847: Fixed an issue with the Hilt Gradle Plugin registered transforms on projects using Gradle 9.0.0 (ea570e7)
• Fixes #4898: Fixed an issue with backwards compatibility handling for libraries that export Hilt roots. (85c470ca4)
• Fixes #4937: Fixed the incorrectly declared version of the Kotlin stdlib dependency in the Hilt Gradle Plugin. (deefd9a2d)
• Updated ASM dependency to 9.8 (365bc499d)

... (truncated)

Commits

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-android-testing from 2.52 to 2.59.2

Release notes

Sourced from com.google.dagger:hilt-android-testing's releases.

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

Dagger 2.59.1

Bug fixes:

• Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
• Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Dagger 2.57.2

Bug fixes

• Fixed #4847: Fixed an issue with the Hilt Gradle Plugin registered transforms on projects using Gradle 9.0.0 (ea570e7)
• Fixes #4898: Fixed an issue with backwards compatibility handling for libraries that export Hilt roots. (85c470ca4)
• Fixes #4937: Fixed the incorrectly declared version of the Kotlin stdlib dependency in the Hilt Gradle Plugin. (deefd9a2d)
• Updated ASM dependency to 9.8 (365bc499d)

... (truncated)

Commits

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

Updates com.google.dagger.hilt.android from 2.52 to 2.59.2

Release notes

Sourced from com.google.dagger.hilt.android's releases.

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

Dagger 2.59.1

Bug fixes:

• Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
• Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Dagger 2.57.2

Bug fixes

• Fixed #4847: Fixed an issue with the Hilt Gradle Plugin registered transforms on projects using Gradle 9.0.0 (ea570e7)
• Fixes #4898: Fixed an issue with backwards compatibility handling for libraries that export Hilt roots. (85c470ca4)
• Fixes #4937: Fixed the incorrectly declared version of the Kotlin stdlib dependency in the Hilt Gradle Plugin. (deefd9a2d)
• Updated ASM dependency to 9.8 (365bc499d)

... (truncated)

Commits

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-compiler from 2.52 to 2.59.2

Release notes

Sourced from com.google.dagger:hilt-compiler's releases.

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

Dagger 2.59.1

Bug fixes:

• Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
• Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Dagger 2.57.2

Bug fixes

• Fixed #4847: Fixed an issue with the Hilt Gradle Plugin registered transforms on projects using Gradle 9.0.0 (ea570e7)
• Fixes #4898: Fixed an issue with backwards compatibility handling for libraries that export Hilt roots. (85c470ca4)
• Fixes #4937: Fixed the incorrectly declared version of the Kotlin stdlib dependency in the Hilt Gradle Plugin. (deefd9a2d)
• Updated ASM dependency to 9.8 (365bc499d)

... (truncated)

Commits

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

Updates androidx.hilt:hilt-navigation-compose from 1.2.0 to 1.3.0

Updates com.squareup.retrofit2:retrofit from 2.11.0 to 3.0.0

Release notes

Sourced from com.squareup.retrofit2:retrofit's releases.

3.0.0

Changed

• Upgrade to OkHttp 4.12 (from 3.14).

  This is the version of OkHttp that is written in Kotlin, and as a result Retrofit now has a transitive Kotlin dependency. However, this is also the supported version of OkHttp whereas the previous version was out of support for nearly 4 years.

Note: The 3.x versions of Retrofit maintain forward binary-compatibility with the 2.x versions. This means libraries compiled against 2.x can still be used with the 3.x versions.

2.12.0

New

• First-party converters now support deferring serialization to happen when the request body is written (i.e., during HTTP execution) rather than when the HTTP request is created. In some cases this moves conversion from a calling thread to a background thread, such as in the case when using Call.enqueue directly.

  The following converters support this feature through a new withStreaming() factory method:

  • Gson
  • Jackson
  • Moshi
  • Protobuf
  • Wire

Fixed

• Primitive types used with @Tag now work by storing the value boxed with the boxed class as the key.

Changelog

Sourced from com.squareup.retrofit2:retrofit's changelog.

3.0.0 - 2025-05-15

Changed

• Upgrade to OkHttp 4.12 (from 3.14).

  This is the version of OkHttp that is written in Kotlin, and as a result Retrofit now has a transitive Kotlin dependency. However, this is also the supported version of OkHttp whereas the previous version was out of support for nearly 4 years.

Note: The 3.x versions of Retrofit maintain forward binary-compatibility with the 2.x versions. This means libraries compiled against 2.x can still be used with the 3.x versions.

2.12.0 - 2025-05-15

New

• First-party converters now support deferring serialization to happen when the request body is written (i.e., during HTTP execution) rather than when the HTTP request is created. In some cases this moves conversion from a calling thread to a background thread, such as in the case when using Call.enqueue directly.

  The following converters support this feature through a new withStreaming() factory method:

  • Gson
  • Jackson
  • Moshi
  • Protobuf
  • Wire

Fixed

• Primitive types used with @Tag now work by storing the value boxed with the boxed class as the key.

Commits

• 3ab0f1a Prepare version 3.0.0
• e5c02d0 Commit 2.x docs (#4378)
• 5bc3f18 Fix links on the proudction site (#4377)
• 7c3b229 Remove compileOnly stdlib dependency (#4376)
• 8418547 Update okhttp monorepo to v4 (major) (#4375)
• 06216a3 Try to fix removal of latest dir during release
• 1697bdc Prepare next development version
• 5a6ce36 Prepare version 2.12.0
• 4fb8aed Fix artifact name (#4372)
• bf11ef4 Dedicated website build, final status job (#4371)
• Additional commits viewable in compare view

Updates com.squareup.retrofit2:converter-gson from 2.11.0 to 3.0.0

Release notes

Sourced from com.squareup.retrofit2:converter-gson's releases.

3.0.0

Changed

• Upgrade to OkHttp 4.12 (from 3.14).

  This is the version of OkHttp that is written in Kotlin, and as a result Retrofit now has a transitive Kotlin dependency. However, this is also the supported version of OkHttp whereas the previous version was out of support for nearly 4 years.

Note: The 3.x versions of Retrofit maintain forward binary-compatibility with the 2.x versions. This means libraries compiled against 2.x can still be used with the 3.x versions.

2.12.0

New

• First-party converters now support deferring serialization to happen when the request body is written (i.e., during HTTP execution) rather than when the HTTP request is created. In some cases this moves conversion from a calling thread to a background thread, such as in the case when using Call.enqueue directly.

  The following converters support this feature through a new withStreaming() factory method:

  • Gson
  • Jackson
  • Moshi
  • Protobuf
  • Wire

Fixed

• Primitive types used with @Tag now work by storing the value boxed with the boxed class as the key.

Changelog

Sourced from com.squareup.retrofit2:converter-gson's changelog.

3.0.0 - 2025-05-15

Changed

• Upgrade to OkHttp 4.12 (from 3.14).

  This is the version of OkHttp that is written in Kotlin, and as a result Retrofit now has a transitive Kotlin dependency. However, this is also the supported version of OkHttp whereas the previous version was out of support for nearly 4 years.

Note: The 3.x versions of Retrofit maintain forward binary-compatibility with the 2.x versions. This means libraries compiled against 2.x can still be used with the 3.x versions.

2.12.0 - 2025-05-15

New

• First-party converters now support deferring serialization to happen when the request body is written (i.e., during HTTP execution) rather than when the HTTP request is created. In some cases this moves conversion from a calling thread to a background thread, such as in the case when using Call.enqueue directly.

  The following converters support this feature through a new withStreaming() factory method:

  • Gson
  • Jackson
  • Moshi
  • Protobuf
  • Wire

Fixed

• Primitive types used with @Tag now work by storing the value boxed with the boxed class as the key.

Commits

• 3ab0f1a Prepare version 3.0.0
• e5c02d0 Commit 2.x docs (#4378)
• 5bc3f18 Fix links on the proudction site (#4377)
• 7c3b229 Remove compileOnly stdlib dependency (#4376)
• 8418547 Update okhttp monorepo to v4 (major) (#4375)
• 06216a3 Try to fix removal of latest dir during release
• 1697bdc Prepare next development version
• 5a6ce36 Prepare version 2.12.0
• 4fb8aed Fix artifact name (#4372)
• bf11ef4 Dedicated website build, final status job (#4371)
• Additional commits viewable in compare view

Updates com.squareup.retrofit2:converter-gson from 2.11.0 to 3.0.0

Release notes

Sourced from com.squareup.retrofit2:converter-gson's releases.

3.0.0

Changed

• Upgrade to OkHttp 4.12 (from 3.14).

  This is the version of OkHttp that is written in Kotlin, and as a result Retrofit now has a transitive Kotlin dependency. However, this is also the supported version of OkHttp whereas the previous version was out of support for nearly 4 years.

Note: The 3.x versions of Retrofit maintain forward binary-compatibility with the 2.x versions. This means libraries compiled against 2.x can still be used with the 3.x versions.

2.12.0

New

• First-party converters now support deferring serialization to happen when the request body is written (i.e., during HTTP execution) rather than when the HTTP request is created. In some cases this moves conversion from a calling thread to a background thread, such as in the case when using Call.enqueue directly.

  The following converters support this feature through a new withStreaming() factory method:

  • Gson
  • Jackson
  • Moshi
  • Protobuf
  • Wire

Fixed

• Primitive types used with @Tag now work by storing the value boxed with the boxed class as the key.

Changelog

Sourced from com.squareup.retrofit2:converter-gson's changelog.

3.0.0 - 2025-05-15

Changed

• Upgrade to OkHttp 4.12 (from 3.14).

  This is the version of OkHttp that is written in Kotlin, and as a result Retrofit now has a transitive Kotlin dependency. However, this is also the supported version of OkHttp whereas the previous version was out of support for nearly 4 years.

Note: The 3.x versions of Retrofit maintain forward binary-compatibility with the 2.x versions. This means libraries compiled against 2.x can still be used with the 3.x versions.

2.12.0 - 2025-05-15

New

• First-party converters now support deferring serialization to happen when the request body is written (i.e., during HTTP execution) rather than when the HTTP request is created. In some cases this moves conversion from a calling thread to a background thread, such as in the case when using Call.enqueue directly.

  The following converters support this feature through a new withStreaming() factory method:

  • Gson
  • Jackson
  • Moshi
  • Protobuf
  • Wire

Fixed

• Primitive types used with @Tag now work by storing the value boxed with the boxed class as the key.

Commits

• 3ab0f1a Prepare version 3.0.0
• e5c02d0 Commit 2.x docs (#4378)
• 5bc3f18 Fix links on the proudction site (#4377)
• 7c3b229 Remove compileOnly stdlib dependency (#4376)
• 8418547 Update okhttp monorepo to v4 (major) (#4375)
• 06216a3 Try to fix removal of latest dir during release
• 1697bdc Prepare next development version
• 5a6ce36 Prepare version 2.12.0
• 4fb8aed Fix artifact name (#4372)
• bf11ef4 Dedicated website build, final status job (#4371)
• Additional commits viewable in compare view

Updates com.squareup.okhttp3:okhttp from 4.12.0 to 5.3.2

Changelog

Sourced from com.squareup.okhttp3:okhttp's changelog.

Version 5.3.2

2025-11-18

• Fix: Don't delay triggering timeouts. In Okio 3.16.0 we introduced a regression that caused timeouts to fire later than they were supposed to.

• Upgrade: [Okio 3.16.4][okio_3_16_4].

Version 5.3.1

2025-11-16

This release is the same as 5.3.0. Okio 3.16.3 didn't have a necessary fix!

• Upgrade: [Okio 3.16.3][okio_3_16_3].

Version 5.3.0

2025-10-30

• New: Add tags to Call, including computable tags. Use this to attach application-specific metadata to a Call in an EventListener or Interceptor. The tag can be read in any other EventListener or Interceptor.

    override fun intercept(chain: Interceptor.Chain): Response {
      chain.call().tag(MyAnalyticsTag::class) {
        MyAnalyticsTag(...)
      }
  return chain.proceed(chain.request())
  
  }

• New: Support request bodies on HTTP/1.1 connection upgrades.

• New: EventListener.plus() makes it easier to observe events in multiple listeners.

• Fix: Don't spam logs with ‘Method isLoggable in android.util.Log not mocked.’ when using OkHttp in Robolectric and Paparazzi tests.

• Upgrade: [Kotlin 2.2.21][kotlin_2_2_21].

• Upgrade: [Okio 3.16.2][okio_3_16_2].

• Upgrade: [ZSTD-KMP 0.4.0][zstd_kmp_0_4_0]. This update fixes a bug that caused APKs to fail [16 KB ELF alignment checks][elf_alignment].

Version 5.2.3

2025-11-18

... (truncated)

Commits

• 75b9c26 Prepare for release 5.3.2.
• ab48e5d Okio 3.16.4 (#9200)
• a9a4638 Prepare next development version.
• ef72228 Prepare for release 5.3.1.
• 6747167 Update com.squareup.okio to v3.16.3 (#9197)
• 0960b47 Prepare for release 5.3.0.
• bfb24eb Support Request Bodies on HTTP1.1 Connection Upgrades (#9159)
• cf4a864 Update Gradle to v9.2.0 (#9171)
• 4e7dbec Update dependency com.puppycrawl.tools:checkstyle to v12.1.1 (#9169)
• 0470853 Add tags to calls, including computable tags (#9168)
• Additional commits viewable in compare view

Updates com.squareup.okhttp3:logging-interceptor from 4.12.0 to 5.3.2

Changelog

Sourced from com.squareup.okhttp3:logging-interceptor's changelog.

Version 5.3.2

2025-11-18

• Fix: Don't delay triggering timeouts. In Okio 3.16.0 we introduced a regression that caused timeouts to fire later than they were supposed to.

• Upgrade: [Okio 3.16.4][okio_3_16_4].

Version 5.3.1

2025-11-16

This release is the same as 5.3.0. Okio 3.16.3 didn't have a necessary fix!

• Upgrade: [Okio 3.16.3][okio_3_16_3].

Version 5.3.0

2025-10-30

• New: Add tags to Call, including computable tags. Use this to attach application-specific metadata to a Call in an EventListener or Interceptor. The tag can be read in any other EventListener or Interceptor.

    override fun intercept(chain: Interceptor.Chain): Response {
      chain.call().tag(MyAnalyticsTag::class) {
        MyAnalyticsTag(...)
      }
  return chain.proceed(chain.request())
  
  }

• New: Support request bodies on HTTP/1.1 connection upgrades.

• New: EventListener.plus() makes it easier to observe events in multiple listeners.

• Fix: Don't spam logs with ‘Method isLoggable in android.util.Log not mocked.’ when using OkHttp in Robolectric and Paparazzi tests.

• Upgrade: [Kotlin 2.2.21][kotlin_2_2_21].

• Upgrade: [Okio 3.16.2][okio_3_16_2].

• Upgrade: [ZSTD-KMP 0.4.0][zstd_kmp_0_4_0]. This update fixes a bug that caused APKs to fail [16 KB ELF alignment checks][elf_alignment].

Version 5.2.3

2025-11-18

... (truncated)

Commits

• 75b9c26 Prepare for release 5.3.2.
• ab48e5d Okio 3.16.4 (#9200...

  Description has been truncated