Repository navigation
Update dependency com.google.devtools.ksp to v2.3.12 - #1346
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/ksp-monorepo
branch
from
August 11, 2026 19:45
bd4027e to
c88cf2b
Compare
renovate
Bot
force-pushed
the
renovate/ksp-monorepo
branch
2 times, most recently
from
August 26, 2026 16:11
afadf0e to
f869003
Compare
renovate
Bot
force-pushed
the
renovate/ksp-monorepo
branch
2 times, most recently
from
September 10, 2026 01:54
dafade1 to
e65add6
Compare
renovate
Bot
force-pushed
the
renovate/ksp-monorepo
branch
3 times, most recently
from
September 21, 2026 16:23
fadfd98 to
168f79e
Compare
Owner
|
@renovate rebase |
renovate
Bot
force-pushed
the
renovate/ksp-monorepo
branch
2 times, most recently
from
October 1, 2026 14:34
9ef69b1 to
3dec513
Compare
renovate
Bot
force-pushed
the
renovate/ksp-monorepo
branch
2 times, most recently
from
October 19, 2026 12:28
5e1d425 to
b7789af
Compare
Owner
|
@renovate rebase |
renovate
Bot
force-pushed
the
renovate/ksp-monorepo
branch
from
October 26, 2026 17:55
b7789af to
29088fc
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.3.10→2.3.12Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
google/ksp (com.google.devtools.ksp)
v2.3.12Compare Source
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 aKSBackingFieldif the given annotation targeted a field. Previously, if a field were targeted, the function would return aKSProperty.Resolver.effectiveJavaModifiers: The function returns fewer modifiers for aKSPropertyDeclarationif 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 theKSBackingFieldobtained 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):
registerProcessorForNewFeaturesfunction inSymbolProcessorEnvironmentimmediately when created (and only once). Example: AbstractTestProcessor.kt#L30KSVisitorshould move toKSVisitorNext. If their processor code does not directly implement the interface but instead extends one of the KSP-provided visitors (such asKSTopDownVisitor), they should instead extendKSTopDownVisitor(enableNewFeatures = true)and overridevisitBackingFielddepending on their code and needs.Let us know if you run into unexpected behavior!
Bug Fixes
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
v2.3.11Compare Source
What's Changed
org.gradle.isolated-projectsfor project isolation (#3051)kspDebugAndroidTesttask skipping on Android library modules (#3050)@NotNullannotations during incremental compilation (#3030)KspGradleConfig.logLevelas@Internal(#3039)org.gradle.isolated-projects=trueto KSP Gradle properties reference table (#3076)KSValueArgument.value(#3069)ksp.useKSP2deprecation notice (#3066)Contributors
Full Changelog: google/ksp@2.3.10...2.3.11
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.