A modern programming language that makes developers happier.

kotlinlang

Hi <https://github.com/google/ksp/releases/tag/2.0.0-1.0.23|here> is the KSP 2.0.0-1.0.23 release
Release note:
*Issues fixed*
• [KSP2] Nullable type arg type becomes non-null after replace() call <https://github.com/google/ksp/issues/1856|#1856>
• Annotations on enum entires on K2 are missing <https://github.com/google/ksp/issues/1962|#1962>
• Got IllegalStateException when calling replace() on error types <https://github.com/google/ksp/issues/1960|#1960>
• [KSP2] Resolver.getJvmCheckedException doesn’t work on property accessors <https://github.com/google/ksp/issues/1900|#1900>
• [KSP2] Property getter JVM names in data classes become componentN instead of getXXX <https://github.com/google/ksp/issues/1958|#1958>
• [KSP2] Resolver.mapToJvmSignature doesn’t unwrap inline classes <https://github.com/google/ksp/issues/1859|#1859>
• [KSP2] KSFunctionDeclaration.asMemberOf does not return correct types <https://github.com/google/ksp/issues/1919|#1919>
• implement getOwnerJvmClassName <https://github.com/google/ksp/pull/1979|#1979>
• [KSP2] KSPropertyDeclaration.hasBackingField returns inconsistent results <https://github.com/google/ksp/issues/1939|#1939>
• [KSP2] Annotations on extension receivers are missing <https://github.com/google/ksp/issues/1899|#1899>
we will also have KSP 1.0.23 for 2.0.20-Beta2 and 2.0.10-RC shortly later today.

After updating I started getting the following error:

```For TYPE_REFERENCE with text `InjectTypeAlias`, unexpected element of type: FirAnnotationCallImpl found```
It's kind of hard to tell what is going on with that because most of my project still fails from <https://github.com/google/ksp/issues/885>.

I can debug / file an issue when I get back to my computer, but thought I'd throw it here in case anything stands out.

Thanks for the heads up, we had major rework of how KSP2 handles annotations with this release, it is possible to see breaking changes, a reproduce will certainly helps with our investigation.

It's happening in <https://github.com/evant/kotlin-inject/pull/350>

&gt; it is possible to see breaking changes
Would it make sense to follow semver to expect those possible breaking changes when upgrading?

I also get &gt; Task :shared:kspDebugKotlinAndroid FAILED  
e: [ksp] java.util.NoSuchElementException: Collection contains no element matching the predicate.

re: expect possible breaking change when upgrading:

No we try to avoid breaking changes if possible, this is more like a regression caused from KSP2's rework of some underlying implementation around annotations, we are investigating.