build(deps): bump the maven-dependencies group across 1 directory with 7 updates

[dependabot]

Bumps the maven-dependencies group with 7 updates in the / directory:

Package	From	To
gradle-wrapper	9.7.0	9.7.1
androidx.compose:compose-bom	2026.08.00	2026.09.00
io.coil-kt.coil3:coil-compose	3.5.0	3.6.3
com.android.application	9.3.1	9.4.1
com.google.devtools.ksp	2.3.11	2.3.12
org.jetbrains.kotlin.android	2.4.10	2.4.20
org.jetbrains.kotlin.plugin.compose	2.4.10	2.4.20
org.jetbrains.kotlin.plugin.compose	2.4.10	2.4.20

Updates gradle-wrapper from 9.7.0 to 9.7.1

Release notes

Sourced from gradle-wrapper's releases.

9.7.1

The Gradle team is excited to announce Gradle 9.7.1.

This is a patch release for 9.7.0. We recommend using 9.7.1 instead of 9.7.0.

Here are the highlights of 9.7.0 release:

• Isolated Projects graduates to incubating
• Broader Configuration Cache compatibility
• Resilient Sync helps you fix broken builds
• More source locations in problem reports

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle: Adam, Aman Gautam, Aman Kumar, Anton Dubrouski, Aurimas, gbhavya07, Josh Friend, nicklauslittle-gov, Pragati, project516, Qin Mi, Ravi, sk-reddy17, Suvrat Acharya, Yongshun Ye.

Upgrade instructions

Switch your build to use Gradle 9.7.1 by updating your wrapper:

./gradlew :wrapper --gradle-version=9.7.1 && ./gradlew :wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

Commits

• 92f0512 update fixed issues for 9.7.1 (#38892)
• 820ee75 update fixed issues for 9.7.1
• 82c23f9 Fix annotation parameter ordering problem in KTS (#38878)
• ef11a72 Fix annotation parameter ordering issue
• bb0d8a9 Make relevant tests polyglot (run for multiple DSLs)
• 336e129 Update signing configuration (#38874)
• 4bdf0da Update signing configuration
• cd9b92c List issues resolved in 9.7.1 (#38839)
• 5f4e381 List issues resolved in 9.7.1
• 1e08ab5 Keep type-use annotations in extracted ABI classes (#38810)
• Additional commits viewable in compare view

Updates androidx.compose:compose-bom from 2026.08.00 to 2026.09.00

Updates io.coil-kt.coil3:coil-compose from 3.5.0 to 3.6.3

Release notes

Sourced from io.coil-kt.coil3:coil-compose's releases.

3.6.3

See CHANGELOG.md.

3.6.2

See CHANGELOG.md.

3.6.1

See CHANGELOG.md.

3.6.0

See CHANGELOG.md.

Changelog

Sourced from io.coil-kt.coil3:coil-compose's changelog.

[3.6.3] - September 18, 2026

• Fix builds using Android Gradle Plugin 9.4.0 and R8 failing due to invalid characters in Kotlin module name metadata.

[3.6.2] - September 4, 2026

• Fix DeDupeConcurrentRequestStrategy hanging requests for a key if a waiting request is cancelled. (#3566)
• Fix a JS/WASM linkage error when using Compose Multiplatform 1.13. (#3568)

[3.6.1] - September 1, 2026

• Fix JS builds failing when ES modules are enabled. (#3558)

[3.6.0] - August 26, 2026

• New: Add support for loading blob: URLs (object URLs) on JS/WASM. (#3504)
• New: Add ImageRequest.Builder.allowPartialImage and ImageLoader.Builder.allowPartialImage to configure whether StaticImageDecoder on Android accepts partial images. This is enabled by default, which is the same behavior in previous Coil releases. (#3494)
• Fix AsyncImage crashing when measured with inverted constraints. (#3470)
• Fix Compose filterQuality not being applied to drawable-backed images, including GIFs. (#3469)
• Fix a JS/WASM image decoder memory leak. (#3503)
• Fix images failing to render with GenericViewTarget in R8 9.0+ optimized builds. (#3518)
• Use Runtime.maxMemory() to determine the maximum memory cache size on JVM instead of assuming 512 MB of available memory. (#3458)
• Bundle ProGuard rules with the non-Android JVM artifact. (#3476)
• Update the Android compile SDK to 37.
• Update Kotlin to 2.4.10.
• Update Compose to 1.12.0.
• Update Okio to 3.18.1.
• Update Skiko to 0.150.1.
• Update kotlinx-io-okio to 0.9.1.

Commits

• 29cae3b Prepare version 3.6.3.
• 0f371ca Remove invalid characters from Kotlin module name metadata. (#3587)
• 779ff1b Prepare version 3.6.2.
• b6818d3 Fix deduplicated request cancellation handling (#3566)
• 79ad576 Fix formatting.
• 4b14a54 Use InternalSkikoApi awaitSkiko directly in web worker decoding (#3568)
• 37e267b Migrate to AGP's new DSL. (#3567)
• 4f56bce Replace use of deprecated Gradle API. (#3565)
• 64f486b Update lint to v32.4.0 (#3564)
• 827faea Update dependency com.android.tools.build:gradle to v9.4.0 (#3563)
• Additional commits viewable in compare view

Updates com.android.application from 9.3.1 to 9.4.1

Updates com.google.devtools.ksp from 2.3.11 to 2.3.12

Release notes

Sourced from com.google.devtools.ksp's releases.

2.3.12

What's Changed

Migrating Processors to Support Backing Fields

This release introduces support for explicit backing fields (#2873), which may now be returned by Resolver.getSymbolsWithAnnotation. To prevent breaking existing processors, new language features require an explicit opt-in.

More generally, the KSP API now explicitly models backing fields for properties. The following is an exhaustive list of functions in KSP API where processor may observe the change after opting in:

• Resolver.getSymbolsWithAnnotation: The function now returns a KSBackingField if the given annotation targeted a field. Previously, if a field were targeted, the function would return a KSProperty.
• Resolver.effectiveJavaModifiers: The function returns fewer modifiers for a KSPropertyDeclaration if it has a backing field, since most of the JVM-specific annotations apply to the backing field. If you are interested in the JVM modifiers, you should call the function with the KSBackingField obtained from the property instead.

Additionally, KSP now models Java fields as properties that always have backing fields. Some of the modifiers now apply to the backing field instead.

Processors adapting to new features must opt in via both of the following steps simultaneously (failing to do both may lead to undefined behavior):

1. The processor should call the registerProcessorForNewFeatures function in SymbolProcessorEnvironment immediately when created (and only once). Example: AbstractTestProcessor.kt#L30
2. All implementations of KSVisitor should move to KSVisitorNext. If their processor code does not directly implement the interface but instead extends one of the KSP-provided visitors (such as KSTopDownVisitor), they should instead extend KSTopDownVisitor(enableNewFeatures = true) and override visitBackingField depending on their code and needs.

Let us know if you run into unexpected behavior!

Bug Fixes

• Fix Resolver.getDeclarationsFromPackage returning incomplete declarations from KLibs in Kotlin Multiplatform (#2396)
• Fix KSP CLI process hanging indefinitely when a processor throws an unhandled exception (#3120)
• Fix implicit task dependency error between KSP and Android Lint in Android KMP (#3128)
• Fix NullPointerException by registering PluginProblemReporter as an application service (#3140)
• Do not mark companion objects as JAVA_STATIC in Resolver.effectiveJavaModifiers (#3125)
• Fix JAVA_STATIC modifier resolution for @​JvmStatic members in Resolver.effectiveJavaModifiers (#3124)
• Update minimum supported Android Gradle Plugin (AGP) version to 8.12.0 (#3149)

New Contributors

Thanks to @​KlyneChrysler, @​budindepunk, and everyone who reported bugs and participated in discussions!

Full Changelog: google/ksp@2.3.11...2.3.12

Commits

• a3c3859 Format Resolver file
• a614317 Fix grammatical errors in Resolver doc comments
• c19f255 Merge equal EXPECT NEXT and EXPECT CURRENT in javaBackingFieldUsedInKotlin
• d3df886 Add test for getting default annotation values in KMP
• 3bcac20 Mark testJavaBackingFieldUsedInKotlin as fixed
• e74bb5f Update expected test output in libOrigins
• c9b1d40 Use KSSyntheticJavaBackingFieldImpl in KSPropertyDeclarationImpl
• afefe15 Add KSSyntheticJavaBackingFieldImpl
• 2da07c1 Add test for missing synthetic Java fields
• 7033530 Fix visibility modifiers for Kotlin-based backing fields
• Additional commits viewable in compare view

Updates org.jetbrains.kotlin.android from 2.4.10 to 2.4.20

Updates org.jetbrains.kotlin.plugin.compose from 2.4.10 to 2.4.20

Updates org.jetbrains.kotlin.plugin.compose from 2.4.10 to 2.4.20