Skip to content

build(deps): bump the kotlin group across 1 directory with 7 updates - #54

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/gradle/kotlin-c85edb627a
Open

build(deps): bump the kotlin group across 1 directory with 7 updates#54
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/gradle/kotlin-c85edb627a

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 23, 2026 •
edited
Loading

Copy link
Copy Markdown

Bumps the kotlin group with 7 updates in the / directory:

Package From To
org.jetbrains.kotlinx:kotlinx-collections-immutable 0.5.1 0.5.2
org.jetbrains.kotlinx:kotlinx-serialization-json 1.11.0 1.12.0
org.jetbrains.kotlinx:kotlinx-serialization-protobuf 1.11.0 1.12.0
org.jetbrains.kotlinx:kotlinx-serialization-protobuf 1.11.0 1.12.0
com.google.devtools.ksp:symbol-processing-api 2.3.10 2.3.12
com.google.devtools.ksp 2.3.10 2.3.12
com.google.devtools.ksp 2.3.10 2.3.12
org.jetbrains.kotlin.plugin.compose 2.4.10 2.4.21
org.jetbrains.kotlin.plugin.serialization 2.4.10 2.4.21
org.jetbrains.kotlin.plugin.serialization 2.4.10 2.4.21

Updates org.jetbrains.kotlinx:kotlinx-collections-immutable from 0.5.1 to 0.5.2

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-collections-immutable's releases.

v0.5.2

  • Fixed addingAll, removingAll, retainingAll, intersect, and containsAll on PersistentHashSet, puttingAll on PersistentHashMap, and their builder counterparts returning wrong results when a collision node meets a single element at the bottom trie level #294
  • Fixed puttingAll on PersistentHashMap, and putAll on its builder, keeping the receiver's value for a key that sits in a collision node on both sides #300
  • Fixed PersistentHashSet.equals being asymmetric after intersect, retainingAll, or the builder's retainAll #291
  • Fixed PersistentHashMapBuilder.put of an already stored value invalidating live iterators and making build() return a new map when the key is in a collision node #304
  • Fixed a live iterator of PersistentHashMapBuilder returning the old values after a putAll that only replaces values #308
  • Fixed PersistentOrderedMapBuilder iterators throwing ConcurrentModificationException after MutableMap.MutableEntry.setValue, or a put that only replaces a value, during iteration #307
  • Fixed MutableMap.MutableEntry.setValue on a PersistentOrderedMapBuilder entry re-adding the key after it was removed from the builder #310

Full changelog: Kotlin/kotlinx.collections.immutable@v0.5.1...v0.5.2

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-collections-immutable's changelog.

0.5.2

  • Fixed addingAll, removingAll, retainingAll, intersect, and containsAll on PersistentHashSet, puttingAll on PersistentHashMap, and their builder counterparts returning wrong results when a collision node meets a single element at the bottom trie level #294
  • Fixed puttingAll on PersistentHashMap, and putAll on its builder, keeping the receiver's value for a key that sits in a collision node on both sides #300
  • Fixed PersistentHashSet.equals being asymmetric after intersect, retainingAll, or the builder's retainAll #291
  • Fixed PersistentHashMapBuilder.put of an already stored value invalidating live iterators and making build() return a new map when the key is in a collision node #304
  • Fixed a live iterator of PersistentHashMapBuilder returning the old values after a putAll that only replaces values #308
  • Fixed PersistentOrderedMapBuilder iterators throwing ConcurrentModificationException after MutableMap.MutableEntry.setValue, or a put that only replaces a value, during iteration #307
  • Fixed MutableMap.MutableEntry.setValue on a PersistentOrderedMapBuilder entry re-adding the key after it was removed from the builder #310
Commits
  • 9f961e4 Release v0.5.2
  • 1d00eea Skip the setValue write when the entry's key is gone from the builder (#315)
  • 8a49b20 Count the value overwrites of putAll and keep the stored keys (#312)
  • 59bc873 Count only size changes for the ordered map builder's iterators (#311)
  • 2b9cc44 Return the collision node as is when the put value is already stored (#309)
  • c9a67cb Take the argument's value when two collision nodes share a key (#302)
  • 024f04c Dispatch bulk trie ops to collision helpers at the bottom level (#301)
  • 578f6ed Update kotlinx.benchmark to 0.4.17
  • e72f86e Lift the single remaining element to the root in set retainAll (#293)
  • 1fd89dd Restore commented-out invariant asserts (#290)
  • Additional commits viewable in compare view

Updates org.jetbrains.kotlinx:kotlinx-serialization-json from 1.11.0 to 1.12.0

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's releases.

v1.12.0

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see #3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

The others include:

  • Encode unsigned integer types as positive integers (#3194) (thanks to Eyüp Can Akman)
  • Correctly decode CborLabel values (#3195)
  • Include actual tag info into CborDecodingException (#3197)

Protobuf improvements

Protocol buffers format received a big new feature: support for unknown fields. Using a new ProtoUnknownFieldHolder class, you can now decode and store unknown fields in Protobuf messages to retransmit them back later. See documentation updates and #2860 for details.

... (truncated)

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's changelog.

1.12.0 / 2026-10-19

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see [#3261](Kotlin/kotlinx.serialization#3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

... (truncated)

Commits

Updates org.jetbrains.kotlinx:kotlinx-serialization-protobuf from 1.11.0 to 1.12.0

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-protobuf's releases.

v1.12.0

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see #3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

The others include:

  • Encode unsigned integer types as positive integers (#3194) (thanks to Eyüp Can Akman)
  • Correctly decode CborLabel values (#3195)
  • Include actual tag info into CborDecodingException (#3197)

Protobuf improvements

Protocol buffers format received a big new feature: support for unknown fields. Using a new ProtoUnknownFieldHolder class, you can now decode and store unknown fields in Protobuf messages to retransmit them back later. See documentation updates and #2860 for details.

... (truncated)

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-protobuf's changelog.

1.12.0 / 2026-10-19

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see [#3261](Kotlin/kotlinx.serialization#3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

... (truncated)

Commits

Updates org.jetbrains.kotlinx:kotlinx-serialization-protobuf from 1.11.0 to 1.12.0

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-protobuf's releases.

v1.12.0

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see #3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

The others include:

  • Encode unsigned integer types as positive integers (#3194) (thanks to Eyüp Can Akman)
  • Correctly decode CborLabel values (#3195)
  • Include actual tag info into CborDecodingException (#3197)

Protobuf improvements

Protocol buffers format received a big new feature: support for unknown fields. Using a new ProtoUnknownFieldHolder class, you can now decode and store unknown fields in Protobuf messages to retransmit them back later. See documentation updates and #2860 for details.

... (truncated)

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-protobuf's changelog.

1.12.0 / 2026-10-19

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see [#3261](Kotlin/kotlinx.serialization#3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

... (truncated)

Commits

Updates com.google.devtools.ksp:symbol-processing-api from 2.3.10 to 2.3.12

Release notes

Sourced from com.google.devtools.ksp:symbol-processing-api'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

2.3.11

What's Changed

  • Support org.gradle.isolated-projects for project isolation (#3051)
  • Fix premature kspDebugAndroidTest task skipping on Android library modules (#3050)
  • Fix missing parent declaration exception for @NotNull annotations during incremental compilation (#3030)
  • Clean output directories instead of skipping tasks when processor classpath transitions to empty (#3046)
  • Fix build cache misses by marking KspGradleConfig.logLevel as @Internal (#3039)
  • Add org.gradle.isolated-projects=true to KSP Gradle properties reference table (#3076)
  • Add KSP Gradle properties reference table to README documentation (#3070)
  • Document collection values in KSValueArgument.value (#3069)
  • Update error messaging for ksp.useKSP2 deprecation notice (#3066)

Contributors

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

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 com.google.devtools.ksp from 2.3.10 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

2.3.11

What's Changed

  • Support org.gradle.isolated-projects for project isolation (#3051)
  • Fix premature kspDebugAndroidTest task skipping on Android library modules (#3050)
  • Fix missing parent declaration exception for @NotNull annotations during incremental compilation (#3030)
  • Clean output directories instead of skipping tasks when processor classpath transitions to empty (#3046)
  • Fix build cache misses by marking KspGradleConfig.logLevel as @Internal (#3039)
  • Add org.gradle.isolated-projects=true to KSP Gradle properties reference table (#3076)
  • Add KSP Gradle properties reference table to README documentation (#3070)
  • Document collection values in KSValueArgument.value (#3069)
  • Update error messaging for ksp.useKSP2 deprecation notice (#3066)

Contributors

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

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 com.google.devtools.ksp from 2.3.10 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 ...

    Description has been truncated

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update java code labels Oct 23, 2026
@dependabot dependabot Bot changed the title build(deps): bump the kotlin group across 1 directory with 7 updates chore(deps): bump the kotlin group across 1 directory with 7 updates Oct 26, 2026
@dependabot
dependabot Bot force-pushed the dependabot/gradle/kotlin-c85edb627a branch from eecf728 to 9e266d4 Compare October 26, 2026 06:24
@dependabot dependabot Bot changed the title chore(deps): bump the kotlin group across 1 directory with 7 updates Bump the kotlin group across 1 directory with 7 updates Oct 29, 2026
@dependabot
dependabot Bot force-pushed the dependabot/gradle/kotlin-c85edb627a branch from 9e266d4 to 08ea9b7 Compare October 29, 2026 06:15
@dependabot
build(deps): bump the kotlin group across 1 directory with 7 updates
edeaa78 
Bumps the kotlin group with 7 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [org.jetbrains.kotlinx:kotlinx-collections-immutable](https://github.com/Kotlin/kotlinx.collections.immutable) | `0.5.1` | `0.5.2` |
| [org.jetbrains.kotlinx:kotlinx-serialization-json](https://github.com/Kotlin/kotlinx.serialization) | `1.11.0` | `1.12.0` |
| [org.jetbrains.kotlinx:kotlinx-serialization-protobuf](https://github.com/Kotlin/kotlinx.serialization) | `1.11.0` | `1.12.0` |
| [org.jetbrains.kotlinx:kotlinx-serialization-protobuf](https://github.com/Kotlin/kotlinx.serialization) | `1.11.0` | `1.12.0` |
| [com.google.devtools.ksp:symbol-processing-api](https://github.com/google/ksp) | `2.3.10` | `2.3.12` |
| [com.google.devtools.ksp](https://github.com/google/ksp) | `2.3.10` | `2.3.12` |
| [com.google.devtools.ksp](https://github.com/google/ksp) | `2.3.10` | `2.3.12` |
| [org.jetbrains.kotlin.plugin.compose](https://github.com/JetBrains/kotlin) | `2.4.10` | `2.4.21` |
| [org.jetbrains.kotlin.plugin.serialization](https://github.com/JetBrains/kotlin) | `2.4.10` | `2.4.21` |
| [org.jetbrains.kotlin.plugin.serialization](https://github.com/JetBrains/kotlin) | `2.4.10` | `2.4.21` |



Updates `org.jetbrains.kotlinx:kotlinx-collections-immutable` from 0.5.1 to 0.5.2
- [Release notes](https://github.com/Kotlin/kotlinx.collections.immutable/releases)
- [Changelog](https://github.com/Kotlin/kotlinx.collections.immutable/blob/master/CHANGELOG.md)
- [Commits](Kotlin/kotlinx.collections.immutable@v0.5.1...v0.5.2)

Updates `org.jetbrains.kotlinx:kotlinx-serialization-json` from 1.11.0 to 1.12.0
- [Release notes](https://github.com/Kotlin/kotlinx.serialization/releases)
- [Changelog](https://github.com/Kotlin/kotlinx.serialization/blob/master/CHANGELOG.md)
- [Commits](Kotlin/kotlinx.serialization@v1.11.0...v1.12.0)

Updates `org.jetbrains.kotlinx:kotlinx-serialization-protobuf` from 1.11.0 to 1.12.0
- [Release notes](https://github.com/Kotlin/kotlinx.serialization/releases)
- [Changelog](https://github.com/Kotlin/kotlinx.serialization/blob/master/CHANGELOG.md)
- [Commits](Kotlin/kotlinx.serialization@v1.11.0...v1.12.0)

Updates `org.jetbrains.kotlinx:kotlinx-serialization-protobuf` from 1.11.0 to 1.12.0
- [Release notes](https://github.com/Kotlin/kotlinx.serialization/releases)
- [Changelog](https://github.com/Kotlin/kotlinx.serialization/blob/master/CHANGELOG.md)
- [Commits](Kotlin/kotlinx.serialization@v1.11.0...v1.12.0)

Updates `com.google.devtools.ksp:symbol-processing-api` from 2.3.10 to 2.3.12
- [Release notes](https://github.com/google/ksp/releases)
- [Commits](google/ksp@2.3.10...2.3.12)

Updates `com.google.devtools.ksp` from 2.3.10 to 2.3.12
- [Release notes](https://github.com/google/ksp/releases)
- [Commits](google/ksp@2.3.10...2.3.12)

Updates `com.google.devtools.ksp` from 2.3.10 to 2.3.12
- [Release notes](https://github.com/google/ksp/releases)
- [Commits](google/ksp@2.3.10...2.3.12)

Updates `org.jetbrains.kotlin.plugin.compose` from 2.4.10 to 2.4.21
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](JetBrains/kotlin@v2.4.10...v2.4.21)

Updates `org.jetbrains.kotlin.plugin.serialization` from 2.4.10 to 2.4.21
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](JetBrains/kotlin@v2.4.10...v2.4.21)

Updates `org.jetbrains.kotlin.plugin.serialization` from 2.4.10 to 2.4.21
- [Release notes](https://github.com/JetBrains/kotlin/releases)
- [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md)
- [Commits](JetBrains/kotlin@v2.4.10...v2.4.21)

---
updated-dependencies:
- dependency-name: com.google.devtools.ksp
  dependency-version: 2.3.12
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: kotlin
- dependency-name: com.google.devtools.ksp
  dependency-version: 2.3.12
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: kotlin
- dependency-name: com.google.devtools.ksp:symbol-processing-api
  dependency-version: 2.3.12
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: kotlin
- dependency-name: org.jetbrains.kotlin.plugin.compose
  dependency-version: 2.4.21
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: kotlin
- dependency-name: org.jetbrains.kotlin.plugin.serialization
  dependency-version: 2.4.21
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: kotlin
- dependency-name: org.jetbrains.kotlin.plugin.serialization
  dependency-version: 2.4.21
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: kotlin
- dependency-name: org.jetbrains.kotlinx:kotlinx-collections-immutable
  dependency-version: 0.5.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: kotlin
- dependency-name: org.jetbrains.kotlinx:kotlinx-serialization-json
  dependency-version: 1.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: kotlin
- dependency-name: org.jetbrains.kotlinx:kotlinx-serialization-protobuf
  dependency-version: 1.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: kotlin
- dependency-name: org.jetbrains.kotlinx:kotlinx-serialization-protobuf
  dependency-version: 1.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: kotlin
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title Bump the kotlin group across 1 directory with 7 updates build(deps): bump the kotlin group across 1 directory with 7 updates Nov 2, 2026
@dependabot
dependabot Bot force-pushed the dependabot/gradle/kotlin-c85edb627a branch from 08ea9b7 to edeaa78 Compare November 2, 2026 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file java Pull requests that update java code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants