[dependabot]

Bumps com.google.devtools.ksp from 2.3.9 to 2.3.13.

Release notes

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

2.3.13

What's Changed

• Add KSContextParameter and KSFunctionDeclaration.contextParameters to the API (#3216)
• Improve diagnostics by returning last round dismissible errors when KSP fails (#3196)
• Add opt-in processor classloader caching (ksp.classloader.cache.processors=true) to speed up multi-module builds (#3210)
• Avoid clearing binary and library caches between KSP rounds (#3235)
• Optimize classpath scanning, dependency indexing, and package directory lookups during incremental compilation (#3254)
• Backport IntelliJ Platform CoreJarHandler to prevent non-deterministic missing jar entries (#3240)
• Fix getting annotation default values from KLibs in Kotlin Multiplatform (#2356)
• Fix resolving aliased annotations in PsiResolutionStrategy (#2997)
• Fix Gradle project isolation detection when configured via command-line flags (#3188)
• Fix duplicate declaration generation in intermediate Kotlin Multiplatform metadata compilations (#3229)

Contributors

• Thanks to @​alfonsocv12, @​bacecek, @​bcorso, @​cushon, and everyone who reported bugs and participated in discussions!

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

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!

... (truncated)

Commits

• 879aa7d Fix errors in CONTRIBUTING.md
• db9b089 Drop KSObjectManager caches in finally block
• e0228b5 Add test showing missing implementation for KSBackingField in `mapToJvmSign...
• 9c2b150 Add test for KSTypeParameterImpl.bounds on type alias
• a1d9933 Update testVarargAnnotationApplication with more cases
• 7401d5e Add test for vararg annotation application
• 4d87803 Add negative test for incremental compilation with Java classpath references
• 8fc84de Delegate PackageIndex lookups to IncrementalJavaFileManager dependencies index
• f4f3029 Document TARGET_BACKEND and WITH_FIXED_TARGET directives in CONTRIBUTING.md
• 0a4efcf Share IncrementalJavaFileManager dependencies index with finder services
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.62.0 (1)	release

⚙️ sentry-android Build Distribution Settings