Bump com.google.devtools.ksp from 2.1.20-1.0.31 to 2.3.0

[dependabot]

Bumps com.google.devtools.ksp from 2.1.20-1.0.31 to 2.3.0.

Release notes

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

2.3.0

What's Changed

• KSP1 has been deprecated[ #2657](google/ksp#2657)
• KSP version is no longer tied to the Kotlin compiler version (moving away from the old - format). #2658
• KSP is no longer a compiler plugin (like KSP1). It now operates as a more standalone tool built on stable compiler APIs (shared with tools like IntelliJ).
• KSP now has fewer limitations on the Kotlin version in use and allows the KSP team to provide better compatibility to KGP/AGP/Gradle
• Read more about KSP2: https://github.com/google/ksp/blob/main/docs/ksp2.md

Reason for 2.3.0 version name:

• It is independent of Kotlin now
• We wanted to match the Kotlin language version
• It is newer than the latest KSP 2.2.20-2.0.4 release.

Full Changelog: google/ksp@2.2.20-2.0.4...2.3.0

2.2.21-RC-2.0.4

What's Changed

• Upgrade Kotlin version to 2.2.21-RC by @​mkmuir0 in google/ksp#2634

Full Changelog: google/ksp@2.2.20-2.0.4...2.2.21-RC-2.0.4

2.2.21-RC2-2.0.4

What's Changed

• Update Kotlin version to 2.2.21-RC2 by @​mkmuir0 in google/ksp#2653
• Show KSP1 warning only once per project by @​hfmehmed in google/ksp#2655

Full Changelog: google/ksp@2.2.21-RC-2.0.4...2.2.21-RC2-2.0.4

2.2.20-2.0.4

What's Changed

• Unable to build on AGP 8.11.1 using KSP 2.2.20-2.0.3 due to class cast exception #2614

• Resolver#getJvmCheckedException(KSPropertyAccessor) throws IllegalArgumentException #2548

• ClassCastException when building with 2.2.20-2.0.3 #2598

• Replace KaFirStopWorldCacheCleaner with no-op implementation #2626

• BuildConfig values are not available during annotation process after upgrading ksp from 2.2.10-2.0.2 -> 2.2.20-2.0.3 #2597

• Missing Gradle task wiring with 2.2.20-2.0.3 #2595

• 2.2.20-2.0.3 + protobufJavalite build errors #2596

Contributors

Thanks to everyone who reported bugs and participated in discussions!

... (truncated)

Commits

• 15a8803 Rename the 2.0.5-release branch to 2.3.0-release.
• b90c740 Untie from Kotlin versions
• 00acc59 Introduce a dummy compiler plugin artifact
• 7110a90 Remove KSP1 from repository
• fd792af Throw runtime error if ksp2 is disabled
• f82a0b4 Remove KSP1 related logic from gradle plugin
• 29ce41f Update jvmTarget and language version in projects
• 3eb782e Remove KSP1 integration tests
• 8f4997c UPDATE_KOTLIN_VERSION: 2.3.0-Beta1
• 3610835 Update auto-merge branch to 2.0.5
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}